Description of problem: $summary Version-Release number of selected component (if applicable): Current master, I think "forever" How reproducible: Always Steps to Reproduce: 1. engine-setup, accept Yes to 'Configure ovirt-provider-ovn?' 2. engine-cleanup 3. Actual results: ovirt-provider-ovn remains active and up Expected results: I think it should be stopped and disabled, like we do to other services (e.g. engine, ovirt-fence-kdump-listener, etc.). Additional info: Patch to stop and disable should be trivial to write. But perhaps network team has some reservations...
This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly
Verified on =========== ovirt-engine-4.5.0-0.237.el8ev.noarch ovirt-engine-setup-4.5.0-0.237.el8ev.noarch ovirt-provider-ovn-1.2.36-1.el8ev.noarch Before engine-cleanup ===================== [user@ENGINE ~]# systemctl status ovirt-provider-ovn ● ovirt-provider-ovn.service - oVirt OVN provider Loaded: loaded (/usr/lib/systemd/system/ovirt-provider-ovn.service; enabled; vendor preset: disabled) Active: active (running) since Tue 2022-03-22 15:14:22 IST; 20h ago Main PID: 1157 (platform-python) Tasks: 4 (limit: 100733) Memory: 45.0M CGroup: /system.slice/ovirt-provider-ovn.service └─1157 /usr/libexec/platform-python /usr/share/ovirt-provider-ovn/ovirt_provider_ovn.py After engine-cleanup ==================== [user@ENGINE ~]# systemctl status ovirt-provider-ovn ● ovirt-provider-ovn.service - oVirt OVN provider Loaded: loaded (/usr/lib/systemd/system/ovirt-provider-ovn.service; disabled; vendor preset: disabled) Active: inactive (dead)
This bugzilla is included in oVirt 4.5.0 release, published on April 20th 2022. Since the problem described in this bug report should be resolved in oVirt 4.5.0 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.