Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
ovn-controller service is not shipped as enabled (to start at boot), by thus can cause a VM to fail if it has OVN network attached to it after a reboot to the hypervisor.
Version-Release number of selected component (if applicable):
openvswitch-2.7.0-1.el7.x86_64
openvswitch-ovn-host-2.7.0-1.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. on hypervisor, run yum install openvswitch-ovn-host
2. systemctl status ovn-controller
Actual results:
Loaded: loaded (/usr/lib/systemd/system/ovn-controller.service; disabled; vendor preset: disabled)
Expected results:
ovn-controller should be enabled by the RPM installation.
My understanding of packaging guidelines is that only services that do not
require configuration to be functional may be enabled by default. Since
ovn-controller requires configuration in order to be functional, it should
not be enabled by default. See e.g.:
https://fedoraproject.org/wiki/Packaging:DefaultServices
Your application must already be doing the equivalent of "systemctl start
ovn-controller" in order to use this service, is there a reason it cannot
also do "systemctl enable ovn-controller"?
Thanks,
Lance
Dan, could you answer this? On hypervisors - can we change the code of the hook(s) to start ovn-controller service?
Currently, the only thing that triggers ovn-controller start is vdsm-config, which is only used only once during setup of the environment.
I agreed with Lance. Services should not be enabled by default, without a very good reason.
The bug should have been filed on ovirt-provider-ovn-driver.