Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1694213

Summary: Compute Nodes Need br-ex for OVN
Product: Red Hat OpenStack Reporter: Dan Sneddon <dsneddon>
Component: openstack-tripleo-heat-templatesAssignee: Dan Sneddon <dsneddon>
Status: ASSIGNED --- QA Contact: Sasha Smolyak <ssmolyak>
Severity: high Docs Contact:
Priority: high    
Version: 15.0 (Stein)CC: bfournie, dsneddon, mburns, yobshans
Target Milestone: gaKeywords: Triaged
Target Release: 15.0 (Stein)   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Dan Sneddon 2019-03-29 19:31:38 UTC
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):
OSP 15

How reproducible:

Steps to Reproduce:
1. Deploy with existing configs

Actual results:
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.

Expected results:
Compute nodes should have a br-ex bridge (or a different name if the NeutronBridgeMappings are not "datacentre:br-ex").

Additional info:
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.

Comment 3 Bob Fournier 2019-04-11 14:19:03 UTC
*** Bug 1698653 has been marked as a duplicate of this bug. ***