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 <libosvar@redhat.com>
(cherry picked from commit 4ad21fd23a
)
This commit is contained in:
parent
34a15fb4bb
commit
b468514e99
|
@ -28,6 +28,13 @@ ovs-vsctl del-controller {{ ovn_bridge }}
|
|||
# Activate ovn-controller by configuring integration bridge
|
||||
ovs-vsctl set open . external_ids:ovn-bridge={{ ovn_bridge }}
|
||||
|
||||
# WORKAROUND for https://bugzilla.redhat.com/show_bug.cgi?id=1782834
|
||||
# By restarting ovs-vswitchd process, new connection is made based
|
||||
# on the protocols values set in OVS database. OVS 2.13 by default
|
||||
# implements OpenFlow protocols up to 1.5 and 1.5 is the one that
|
||||
# is required by ovn-controller.
|
||||
systemctl restart openvswitch
|
||||
|
||||
podman start ovn_controller
|
||||
|
||||
# Delete ovs bridges - br-tun and br-migration
|
||||
|
|
Loading…
Reference in New Issue