4cb9062319
neutron should rely on nova doing the job instead of trying to 'fix' it. 'Fixing' it introduces race conditions between lb agent and nova VIF driver. Particularly, lb agent can scan for new tap devices in the middle of nova plumbing qbr-tap setup, and attempt to do it on its own. So if agent is more lucky to plug the tap device into the bridge, nova may fail to do the same, getting the following error: libvirtError: Unable to add bridge brqxxx-xx port tapxxx-xx: Device or resource busy This also requires a change in how the port admin_state_up is implemented by setting the tap device's link state instead of moving it in or out of the bridge. Conflicts: neutron/common/constants.py neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py neutron/tests/unit/plugins/ml2/drivers/linuxbridge/agent/test_linuxbridge_neutron_agent.py Co-Authored-By: Sean M. Collins <sean@coreitpro.com> Co-Authored-By: Darragh O'Reilly <darragh.oreilly@hp.com> Co-Authored-By: Andreas Scheuring <andreas.scheuring@de.ibm.com> Closes-Bug: #1312016 (cherry picked from commit |
||
---|---|---|
.. | ||
brocade | ||
embrane | ||
hyperv | ||
ml2 | ||
oneconvergence | ||
opencontrail | ||
__init__.py |