Description of problem:
OVN uses distributed routing by default, similar to how ML2/OVS did DVR. This means that the compute nodes need a br-ex bridge by default, just like the controllers, but with no IP.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Deploy with existing configs
Unless the "compute-dvr.yaml" template is used with the multiple-nics templates, the Compute nodes will have no br-ex and external routing does not work.
Compute nodes should have a br-ex bridge (or a different name if the NeutronBridgeMappings are not "datacentre:br-ex").
We will have multiple releases that need to support both OVS and OVN. We may want to create a mechanism where the bridge is enabled via flag, so that either option can be easily deployed.
*** Bug 1698653 has been marked as a duplicate of this bug. ***
*** Bug 1713464 has been marked as a duplicate of this bug. ***
ovs_neutron_agent in compute node terminates if Bridge br-ex is not present.
2019-05-23 13:22:00.165 24758 ERROR neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [req-08f03002-4bee-4acd-ace2-73097f699c12 - - - - -] Bridge br-ex for physical network datacentre does not exist. Agent terminated!
Created attachment 1573782 [details]
computeovsdpdk sos report
Moving to ON_DEV until patch merges and is backported to stable/stein.
Compute nodes now create correctly with bridge when using OSP15 geneve/DVR
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.