[Bug 1852221] Re: ovs-vswitchd needs to be forced to reconfigure after adding protocols to bridges
Frode Nordahl
1852221 at bugs.launchpad.net
Fri May 22 09:16:51 UTC 2020
** Summary changed:
- ovsdb-server needs to be restarted after adding protocols to bridges
+ ovs-vswitchd needs to be forced to reconfigure after adding protocols to bridges
** Description changed:
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:
+ However, the Open vSwitch `ovs-vswitchd` process does not appear to
+ always update its perspective of which protocol versions it should
+ support for bridges:
# 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)
- # systemctl restart ovsdb-server
+ # systemctl restart ovsdb-server
# ovs-ofctl -O OpenFlow14 dump-flows br-int
- cookie=0x84ead4b79da3289a, duration=1.576s, table=0, n_packets=0, n_bytes=0, priority=65535,vlan_tci=0x0fff/0x1fff actions=drop
- cookie=0x84ead4b79da3289a, 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
+ cookie=0x84ead4b79da3289a, duration=1.576s, table=0, n_packets=0, n_bytes=0, priority=65535,vlan_tci=0x0fff/0x1fff actions=drop
+ cookie=0x84ead4b79da3289a, 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
...
(Success)
- 0:
- https://github.com/openstack/neutron/blob/0fa7e74ebb386b178d36ae684ff04f03bdd6cb0d/neutron/agent/common/ovs_lib.py#L281
+ The restart of the `ovsdb-server` process above will make `ovs-vswitchd`
+ reassess its configuration.
+
+
+ 0: https://github.com/openstack/neutron/blob/0fa7e74ebb386b178d36ae684ff04f03bdd6cb0d/neutron/agent/common/ovs_lib.py#L281
--
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1852221
Title:
ovs-vswitchd needs to be forced to reconfigure after adding protocols
to bridges
Status in OpenStack neutron-openvswitch charm:
Invalid
Status in kolla-ansible:
New
Status in neutron:
New
Status in openvswitch:
New
Status in openvswitch package in Ubuntu:
Confirmed
Bug description:
As part of programming OpenvSwitch, Neutron will add to which
protocols bridges support [0].
However, the Open vSwitch `ovs-vswitchd` process does not appear to
always update its perspective of which protocol versions it should
support for bridges:
# 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)
# systemctl restart ovsdb-server
# ovs-ofctl -O OpenFlow14 dump-flows br-int
cookie=0x84ead4b79da3289a, duration=1.576s, table=0, n_packets=0, n_bytes=0, priority=65535,vlan_tci=0x0fff/0x1fff actions=drop
cookie=0x84ead4b79da3289a, 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
...
(Success)
The restart of the `ovsdb-server` process above will make `ovs-
vswitchd` reassess its configuration.
0: https://github.com/openstack/neutron/blob/0fa7e74ebb386b178d36ae684ff04f03bdd6cb0d/neutron/agent/common/ovs_lib.py#L281
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1852221/+subscriptions
More information about the Ubuntu-openstack-bugs
mailing list