Description of problem:
It was noticed during PerfScale testing on OSP16 deployment.
During manual upgrade of OVN from 2.11 to manually build package from branch 20.06, the ovn-controllers can't connect to previously created bridges, like br-int, because of lack of support for Openflow 1.5 on bridge.
Example error found on ovn-controller logs:
2020-06-03T13:55:20.204Z|00086|rconn|WARN|unix:/var/run/openvswitch/br-int.mgmt: connection dropped (Protocol error)
Bridge was previously created with protocols=.
"ovs-vsctl set bridge br-int protocols=OpenFlow13,OpenFlow15"
OVN-controller is able to connect to the bridge.
Steps to Reproduce:
1. Install OVN with 2.11
2. Create br-int
3. Upgrade OVN to 20.06
ovn-controller can't connect to br-int
ovn-controller should connect to br-int
Possible workaround is to add the protocol OpenFlow15 to the protocols column of br-int - ovs-vsctl add bridge br-int protocols OpenFlow15
clear the protocols colum - "ovs-vsctl clear bridge br-int protocols"
(In reply to Numan Siddique from comment #4)
> Possible workaround is to add the protocol OpenFlow15 to the protocols
> column of br-int - ovs-vsctl add bridge br-int protocols OpenFlow15
> clear the protocols colum - "ovs-vsctl clear bridge br-int protocols"
Neither help because of bug 1782834
Worth to note this happens only when updating OVN to 2.13 while having OVS 2.11.
- OVS 2.11 by default supports OF protocols up to 1.4, and OVN 2.13 connects with OF protocol 1.5.
- OVS 2.13 by default supports OF protocols up to 1.5, so OVN 2.13 has no issues connecting to the integration bridge
- OVS 2.11 doesn't contain the regression described in 1782834 so the workarounds specified in comment 4 should work.