Some OVS bridges may lack OpenFlow10 protocol

Bug #1905538 reported by Oleg Bondarev
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
Oleg Bondarev

Bug Description

After commit OVSAgentBridge.setup_controllers() no longer sets OpenFlow10 protocol for the bridge, instead it was moved to ovs_lib.OVSBridge.create().
However some (custom) OVS bridges could be created by nova/os-vif when plugging VM interface.
For such bridges neutron does not call create(), only setup_controllers() - as a result such bridges support only OpenFlow13 and ovs-ofctl command fails:

2020-11-24T20:18:38Z|00001|vconn|WARN|unix:/var/run/openvswitch/br01711489f-fe.24081.mgmt: version negotiation failed (we support version 0x01, peer supports version 0x04)
ovs-ofctl: br01711489f-fe: failed to connect to socket (Broken pipe)

Fix: return setting of OpenFlow10 (along with OpenFlow13) to setup_controllers(). It's doesn't hurt even if bridge already has OpenFlow10 in supported protocols.

Tags: ovs ovs-lib
Revision history for this message
Rodolfo Alonso (rodolfo-alonso-hernandez) wrote :
Revision history for this message
Oleg Bondarev (obondarev) wrote :
Changed in neutron:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron

This issue was fixed in the openstack/neutron release candidate.

Changed in neutron:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.