With introduction of multi-segment support in ml2 plugin, agent misconfiguration could happen under exceptionnal circumstances:
Supposing a multi-segment provider network is created with different network types (suppose a flat and a vlan segment), and two ports are bound on an agent supporting the associated physical network.
Portbinding validation will occur on network's segments list returned by db.get_network_segments funtion . As this function may not always returns segments in the same order, one port may be bound to the flat segment while the other will be bound to vlan one.
In that case, ports wouldn't be properly plugged in agent, as they'd recieve two contradictory segment details for the same network.
OVS agent would probably bound the two ports within the same segment as they both would use the same LocalVLANMapping
LB agent would probably add two uplink interfaces under the same qbr[net-id] bridge
Hi,
Please provide the steps to reproduce.
Thanks in Advance.