Bug 1241610

Summary:	ERROR: The Parameter (NeutronExternalNetworkBridge) was not defined in template.
Product:	Red Hat OpenStack	Reporter:	James Slagle <jslagle>
Component:	openstack-tripleo-heat-templates	Assignee:	James Slagle <jslagle>
Status:	CLOSED ERRATA	QA Contact:	Ofer Blaut <oblaut>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	Director	CC:	dmacpher, jslagle, kbasil, mburns, ohochman, rhel-osp-director-maint, whayutin
Target Milestone:	ga	Keywords:	Automation
Target Release:	Director
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-0.8.6-32.el7ost	Doc Type:	Known Issue
Doc Text:	Tuskar modified the names of the top level parameters in the Heat stack when deploying an Overcloud. This caused an error during stack validation from Heat: ERROR: The Parameter (NeutronExternalNetworkBridge) was not defined in template. As a workaround, use "tuskar plan-update" to modify the parameter, or use the modified parameter name in the environment file: parameters: Controller-1::NeutronExternalNetworkBridge: "''" Overcloud deploys using the correct parameter value. Note: the parameter needs to be defined in the "parameters:" section, not the "parameter_defaults:" section. Otherwise, the value set in Tuskar's exported environment.yaml overrides the value.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 13:59:05 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 James Slagle 2015-07-09 15:25:53 UTC

Getting this error:

ERROR: The Parameter (NeutronExternalNetworkBridge) was not defined in template.

when deploying via tuskar and nework isolation with environments/net-single-nic-with-vlans.yaml

It's caused b/c NeutronExternalNetworkBridge is a top level parameter, but Tuskar munges the names of the top level parameters.

Comment 3 James Slagle 2015-07-09 15:30:18 UTC

the fix here is to use parameter_defaults in the environment instead of parameters, that way if the parameter does not exist at the top level, we don't get an error.

We're going to need an extra step though to update the Tuskar plan accordingly though.

The command is:
tuskar plan-update 5f8f194c-55c6-4d56-8eb7-ff3a37c5c11f -P Controller-1::NeutronExternalNetworkBridge="''"

note that this is only done when using network isolation and the environments/net-single-nic-with-vlans.yaml and environments/net-bond-with-vlans.yaml files

Comment 4 wes hayutin 2015-07-09 16:57:44 UTC

https://code.engineering.redhat.com/gerrit/#/c/52703/ seems to have fixed the issue.  Waiting now for my overcloud to finish deploying.

Comment 8 Ofer Blaut 2015-07-21 11:29:17 UTC

just tested with      
parameters:
  Controller-1::NeutronExternalNetworkBridge: "''"

and external network works, no error is seen

openstack-tripleo-heat-templates-0.8.6-44.el7ost.noarch

Comment 10 errata-xmlrpc 2015-08-05 13:59:05 UTC

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.

https://access.redhat.com/errata/RHEA-2015:1549