Reviewed: https://review.opendev.org/745122 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=4ad21fd23ae648536c4f07f980e9e156b5c41421 Submitter: Zuul Branch: master
commit 4ad21fd23ae648536c4f07f980e9e156b5c41421 Author: Jakub Libosvar <[email protected]> Date: Thu Aug 6 14:47:24 2020 +0200 migration: Restart OVS after setting protocols This patch is a workaround for bug in OVS [1]. The OVS is restarted after setting protocols for the integration bridge. This will cause a data plane disruption. We can remove the workaround once the bug [1] is fixed. Closes-bug: #1890596 [1] https://bugzilla.redhat.com/show_bug.cgi?id=1782834 Change-Id: Ia635f705fa03036a9e9c1c14eab59038ec39bda3 Signed-off-by: Jakub Libosvar <[email protected]> ** Changed in: neutron Status: In Progress => Fix Released ** Bug watch added: Red Hat Bugzilla #1782834 https://bugzilla.redhat.com/show_bug.cgi?id=1782834 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1890596 Title: ovn-controller cannot connect to the integration bridge with OVS 2.12 and later Status in neutron: Fix Released Bug description: There is a bug in OVS 2.12 and later where protocols cannot be set after bridge is created. OVS agents set explicitly OpenFlow protocols but there is a mismatch with ovn-controller. That means even though the migration process resets the protocols, because of the OVS bug https://bugzilla.redhat.com/show_bug.cgi?id=1782834 ovn-controller can't connect. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1890596/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
