DVR multinode job has linuxbridge agent mech driver defined

[Brian Haley]

There's an ML2 port binding error being generated in the DVR multinode job.

http://logs.openstack.org/50/502850/2/check/gate-grenade-dsvm-neutron-dvr-multinode-ubuntu-xenial-nv/9d7ab88/logs/screen-q-svc.txt.gz#_Sep_12_16_36_00_230807

DEBUG neutron.plugins.ml2.drivers.mech_agent [None req-a68ce697-14fd-497a-9bb6-b55a899a8d54 None None] Port 1f89c2a7-de09-49f7-a298-37b22d37192c on network 3608f5e9-c01b-4791-9a18-90461a614fa8 not bound, no agent of type Linux bridge agent registered on host ubuntu-xenial-2-node-rax-dfw-10898269 {{(pid=26134) bind_port /opt/stack/new/neutron/neutron/plugins/ml2/drivers/mech_agent.py:102}}

ERROR neutron.plugins.ml2.managers [None req-a68ce697-14fd-497a-9bb6-b55a899a8d54 None None] Failed to bind port 1f89c2a7-de09-49f7-a298-37b22d37192c on host ubuntu-xenial-2-node-rax-dfw-10898269 for vnic_type normal using segments []

This is happening because by default, devstack enables the linuxbridge mechanism driver when DVR mode != legacy, even though the linuxbridge agent doesn't work with DVR.

Devstack needs to change to not enable the driver in this case.

[Brian Haley (brian-haley)]

master patch has landed:

    https://review.openstack.org/#/c/503428/

stable/pike in review:

    https://review.openstack.org/#/c/503741/