Comment 8 for bug 1067669

I'm not sure if this bug has affected me, but the fix seems to be affecting me, and I'm now confused about my understanding of the network_vlan_ranges and physical_interface_mappings configs.

My scenario is strictly provider network with a bunch of 802.1q VLANs riding a single bond, managed via quantum-plugin-linuxbridge-agent...for example, my working config prior to the patch that fixed this bug was:

network_vlan_ranges = DEV_WDMZ,DEV_APP,DEV_DB,DEV_ADMIN,DEV_STOR,DEV_WDMZSTOR,DEV_ADMZSTOR,DEV_FWEBDMZ,DEV_FWEBDMZSTOR,DEV_FDMZSTOR,DEV_ADMZ,DEV_FDMZ

physical_interface_mappings = DEV_WDMZ:bond0,DEV_APP:bond0,DEV_DB:bond0,DEV_ADMIN:bond0,DEV_STOR:bond0,DEV_WDMZSTOR:bond0,DEV_ADMZSTOR:bond0,DEV_FWEBDMZ:bond0,DEV_FWEBDMZSTOR:bond0,DEV_FDMZSTOR:bond0,DEV_ADMZ:bond0,DEV_FDMZ:bond0

After this patch, the agent fails on startup citing what would seem to be my duplicate usage of bond0:

2013-03-06 17:46:33 ERROR [quantum.plugins.linuxbridge.agent.linuxbridge_quantum_agent] Parsing physical_interface_mappings failed: Value bond0 in mapping: 'DEV_APP:bond0' not unique. Agent terminated!

It seems that a duplication of the interface value should be a nonissue? This worked fine previously, so if someone can explain how my linuxbridge config should look for multiple network attachment to the same interface I'd appreciate it.