Bridges keep controller settings after reboot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
os-net-config |
Fix Released
|
High
|
Jakub Libosvar |
Bug Description
Bridge configuration settings consume a fail_mode that is set when node boots. Sometimes, bridge may be used for control plane traffic/management network, such bridges are put to standalone mode. neutron-
From man ovs-vsctl(8): "If the value is standalone, or if neither of these settings is set, ovs-vswitchd will take over responsibility for setting up flows when no message has been received from the controller for three times the inactivity probe interval."
In case node is rebooted, bridge is on boot set to standalone but controller address is persistently stored in ovsdb and once openvswitch-agent starts, it will attempt to communicate via bridge with server. As bridge in standalone mode has access to the controller (ovs-agent), it won't be managed by ovs-vswitchd and won't let ovs-agent communicate with server. Hence agent won't get information about bridges settings and that creates a chicken-egg problem.
The solution would be to delete controller along with setting bridge to standalone.
Changed in os-net-config: | |
status: | Triaged → Fix Committed |
tags: | added: ocata-backport-potential |
Changed in os-net-config: | |
status: | Fix Committed → Fix Released |
Review request: https:/ /review. openstack. org/#/c/ 495919/