Bug 1683098

Summary: ovirt-provider-ovn service is not stopped/disabled by engine-cleanup
Product: [oVirt] ovirt-engine Reporter: Yedidyah Bar David <didi>
Component: Setup.EngineAssignee: Ales Musil <amusil>
Status: CLOSED CURRENTRELEASE QA Contact: msheena
Severity: medium Docs Contact:
Priority: medium    
Version: 4.2.3CC: bugs, dholler, mburman, mperina
Target Milestone: ovirt-4.5.0Flags: pm-rhel: ovirt-4.5?
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.5.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-20 06:33:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Yedidyah Bar David 2019-02-26 09:21:22 UTC 
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...
Comment 1 Michal Skrivanek 2020-03-18 15:47:04 UTC 
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
Comment 2 Michal Skrivanek 2020-03-18 15:51:49 UTC 
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
Comment 3 msheena 2022-03-23 10:07:20 UTC 
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)
Comment 4 Sandro Bonazzola 2022-04-20 06:33:59 UTC 
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.