-
Bug
-
Resolution: Unresolved
-
High
-
None
-
Oxygen-SR1
-
OS: Linux 4.2.0-34-generic #39~14.04.1-Ubuntu SMP Fri Mar 11 11:38:02 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Open vSwitch: 2.8.1
Opendaylight: Carbon-SR2
Hello,
I found a bug when using ODL to manage multiple bridges on a single OVS.
The problem is as follows:
- I create two bridges br1 and br2 on an OVS node and set them to use OpenFlow 1.3 by setting a ProtocolEntry with OvsdbBridgeProtocolOpenflow13.class in OvsdbBridgeAugmentationBuilder.
- Setting the ProtocolEntry is required because OVS 2.8.1 defaults to a version of OpenFlow not supported by ODL
- I then delete bridge br2 through the OVSDB REST API
- At that point, br2 is correctly deleted but br1 gets disconnected from ODL OpenFlow plugin
The following line appears in the log:
2018-02-09 17:41:42,787 | INFO | on-dispatcher-61 | ProtocolRemovedCommand | 345 - org.opendaylight.ovsdb.southbound-impl - 1.4.2.Carbon | Removed ProtocolEntry : OpenFlow13 for OVSDB Bridge : null
instead of something like
2018-02-09 17:41:42,787 | INFO | on-dispatcher-61 | ProtocolRemovedCommand | 345 - org.opendaylight.ovsdb.southbound-impl - 1.4.2.Carbon | Removed ProtocolEntry : OpenFlow13 for OVSDB Bridge : br2
When checking the ovsdb topology through the REST API, it appears that the ProtocolEntry has been removed for br1 as well
It is possible to get back the connectivity using
ovs-vsctl set bridge br1 protocols=OpenFlow13
but that requires manual action on the OVS.
Do not hesitate to contact me if more info is required.
Thanks
Thomas