The linuxbridge agent for Neutron expects that the public bridge will already be created by the time it starts. On devstack, this only occurs as part of the l3 agent configuration. If a compute node doesn't have an l3 agent and is using a linuxbridge agent, then br-ex won't be created and the process will not be able to start (causing stack.sh to fail). This causes the gate-grenade-dsvm-neutron-linuxbridge-multinode-nv gate to fail. To avoid the issue, skip the bridge mappings setup unless L3 is configured. This is done in a backward compatible fashion: if localrc uses the old q-l3 tags, the is_service_enabled neutron-l3 would not be able to succeed. Closes-Bug: #1643562 Change-Id: I292ff0dc080fb84b5f879ba2f00f03eff295b55b
3.5 KiB
3.5 KiB