Bug 1244877

Summary:	Tuskar does not respect the NeutronExternalNetworkBridge parameter in network environment
Product:	Red Hat OpenStack	Reporter:	Dan Sneddon <dsneddon>
Component:	rhosp-director	Assignee:	Ana Krivokapic <akrivoka>
Status:	CLOSED WONTFIX	QA Contact:	yeylon <yeylon>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0 (Kilo)	CC:	mburns, rhel-osp-director-maint, srevivo
Target Milestone:	z1	Keywords:	ZStream
Target Release:	Director
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-19 16:46:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dan Sneddon 2015-07-20 16:44:16 UTC

Description of problem:
When configuring the network-environment.yaml file, the NeutronExternalNetworkBridge can be specified. It defaults to "br-ex", but in most cases we will want to use a VLAN interface instead, so the bridge mapping should be "''". Tuskar, however, seems to ignore this parameter unless we prefix it like: Controller-1::NeutronExternalNetworkBridge.

Version-Release number of selected component (if applicable):
puddle-2015-07-17.2

How reproducible:
100%

Steps to Reproduce:
1. Add to parameter_defaults section of network-environment.yaml:   NeutronExternalNetworkBridge: "''"
2. Deploy overcloud with tuskar
3.

Actual results:
Overcloud l3agent.ini still has in l3_agent.ini:
external_network_bridge = br-ex

Expected results:
l3_agent.ini:external_network_bridge = 

Additional info:
We don't have to prefix Controller-1:: on any other parameters, so I'm not sure what's going on here. Apparently there used to be a CLI parameter for this, but it got removed.

Comment 3 Mike Burns 2015-08-19 16:46:34 UTC

Things are working as expected and we're going to be moving away from tuskar.