Red Hat Bugzilla – Bug 1464867
ovn-controller is not configured to start at boot
Last modified: 2017-06-29 04:16:24 EDT
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):
Steps to Reproduce:
1. on hypervisor, run yum install openvswitch-ovn-host
2. systemctl status ovn-controller
Loaded: loaded (/usr/lib/systemd/system/ovn-controller.service; disabled; vendor preset: disabled)
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.:
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"?
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.
We also don't enable OVS by default.
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.
*** This bug has been marked as a duplicate of bug 1466169 ***