As part of programming OpenvSwitch, Neutron will add to which protocols bridges support [0].
However, the Open vSwitch `ovsdb-server` process does not appear to update its perspective of which protocol versions it should support until it is restarted:
# ovs-ofctl -O OpenFlow14 dump-flows br-int
2019-11-12T12:52:56Z|00001|vconn|WARN|unix:/var/run/openvswitch/br-int.mgmt: version negotiation failed (we support version 0x05, peer supports version 0x01)
ovs-ofctl: br-int: failed to connect to socket (Broken pipe)
As part of programming OpenvSwitch, Neutron will add to which protocols bridges support [0].
However, the Open vSwitch `ovsdb-server` process does not appear to update its perspective of which protocol versions it should support until it is restarted:
# ovs-ofctl -O OpenFlow14 dump-flows br-int 12T12:52: 56Z|00001| vconn|WARN| unix:/var/ run/openvswitch /br-int. mgmt: version negotiation failed (we support version 0x05, peer supports version 0x01)
2019-11-
ovs-ofctl: br-int: failed to connect to socket (Broken pipe)
# systemctl restart ovsdb-server 0x84ead4b79da32 89a, duration=1.576s, table=0, n_packets=0, n_bytes=0, priority= 65535,vlan_ tci=0x0fff/ 0x1fff actions=drop 0x84ead4b79da32 89a, duration=1.352s, table=0, n_packets=0, n_bytes=0, priority= 5,in_port= "int-br- ex",dl_ dst=fa: 16:3f:69: 2e:c6 actions= goto_table: 4
# ovs-ofctl -O OpenFlow14 dump-flows br-int
cookie=
cookie=
...
(Success)
0: https:/ /github. com/openstack/ neutron/ blob/0fa7e74ebb 386b178d36ae684 ff04f03bdd6cb0d /neutron/ agent/common/ ovs_lib. py#L281