The LACP code uses the bridge's datapath ID as it's system ID when
something else hasn't been explicitly configured. Since LACP was
configured before each bridge's datapath ID, the LACP module would
be configured with a datapath ID of zero which broke basic LACP
support.
Future patches will add tests which would have caught the issue.
Bug #8516.
---
vswitchd/bridge.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/vswitchd/bridge.c b/vswitchd/bridge.c
index d085f47..ccff405 100644
--- a/vswitchd/bridge.c
+++ b/vswitchd/bridge.c
@@ -444,6 +444,8 @@ bridge_reconfigure(const struct ovsrec_open_vswitch
*ovs_cfg)
HMAP_FOR_EACH (br, node, &all_bridges) {
struct port *port;
+ bridge_configure_datapath_id(br);
+
HMAP_FOR_EACH (port, hmap_node, &br->ports) {
struct iface *iface;
@@ -456,7 +458,6 @@ bridge_reconfigure(const struct ovsrec_open_vswitch
*ovs_cfg)
}
}
bridge_configure_mirrors(br);
- bridge_configure_datapath_id(br);
bridge_configure_flow_eviction_threshold(br);
bridge_configure_forward_bpdu(br);
bridge_configure_remotes(br, managers, n_managers);
--
1.7.7
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
