Bug 1268070

Summary:	EC2MetadataIp and ControlPlaneDefaultRoute Have No Default Value
Product:	Red Hat OpenStack	Reporter:	Dan Sneddon <dsneddon>
Component:	openstack-tripleo-heat-templates	Assignee:	Dan Sneddon <dsneddon>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Shai Revivo <srevivo>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	7.0 (Kilo)	CC:	hbrock, jcoufal, mburns, mcornea, psanchez, rhel-osp-director-maint
Target Milestone:	---
Target Release:	10.0 (Newton)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-10-05 21:41: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 Dan Sneddon 2015-10-01 18:21:10 UTC

Description of problem:
The recently-added EC2MetadataIp has no default value. This means that you can't launch a stack by simply including the network-isolation.yaml and net-single-nic-with-vlans.yaml, you need a network environment file.

Version-Release number of selected component (if applicable):
openstack-tripleo-heat-templates.noarch    0.8.6-70.el7ost        @rhelosp-7.0-director-puddle


How reproducible:
100%

Steps to Reproduce:
1. Deploy with "openstack overcloud deploy -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/net-single-nic-with-vlans.yaml <other_params>
2.
3.

Actual results:
Stack failed with status: Resource CREATE failed: resources[0]: resources.Compute.Property error: resources.NetworkConfig.properties: Property ControlPlaneDefaultRoute not assigned


Expected results:
We used to have defaults defined for all values that worked well for CI and testing. Now, we can't deploy with default values unless there is a network-environment.yaml file. We either need a default network-environment.yaml inside of the environments folder, or we need to have defaults for these new parameters.

Additional info:

Comment 3 Mike Burns 2016-04-07 20:54:03 UTC

This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.