Description of problem: After upgrade of an ovirt host from 4.2 to 4.3, the ovn-controller service is stopped, which results in networking issues. Version-Release number of selected component (if applicable): rhv-openvswitch-2.10-5.el7ev.noarch How reproducible: always Steps to Reproduce: 1. upgrade ovirt node from 4.2 to 4.3 2. check the status of the ovn-controller service (systemctl status ovn-controller) Actual results: inactive Expected results: active Additional info: (re)starting the ovn-controller service worked as expected
http://pkgs.devel.redhat.com/cgit/rpms/rhv-openvswitch/commit/?h=rhevm-4.3-rhel-7&id=c70a592369fd786937d5559c116f289fdee3d396 adds ovn-controller to the list of tracked services.
(In reply to Dan Kenigsberg from comment #2) > http://pkgs.devel.redhat.com/cgit/rpms/rhv-openvswitch/commit/?h=rhevm-4.3- > rhel-7&id=c70a592369fd786937d5559c116f289fdee3d396 adds ovn-controller to > the list of tracked services. Please note that the link you provided is to 2.10-6 rhv-python-openvswitch.noarch 1:2.10-6.el7ev and not 2.11 Tested upgrade flow 4.2(2.9) > 4.3(2.10) The ovn-controller is alive after upgrade
Verified on - rhv-openvswitch-2.10-6.el7ev.noarch rhv-openvswitch-ovn-host-2.10-6.el7ev.noarch rhv-openvswitch-ovn-common-2.10-6.el7ev.noarch rhv-python-openvswitch-2.10-6.el7ev.noarch upgrade from rhv-release-4.2.8-11-001.noarch >> rhv-release-4.3.4-1-001.noarch ovs 2.9 >> ovs 2.10-6 ovn-controller is restarted and alive after update ● ovn-controller.service - OVN controller daemon Loaded: loaded (/usr/lib/systemd/system/ovn-controller.service; enabled; vendor preset: disabled) Active: active (running) since Sun 2019-05-19 14:09:25 IDT; 1min 3s ago Process: 23058 ExecStart=/usr/share/openvswitch/scripts/ovn-ctl --no-monitor start_controller $OVN_CONTROLLER_OPTS (code=exited, status=0/SUCCESS) Main PID: 23088 (ovn-controller) Tasks: 3 CGroup: /system.slice/ovn-controller.service
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:1562