Red Hat Bugzilla – Bug 1268070
EC2MetadataIp and ControlPlaneDefaultRoute Have No Default Value
Last modified: 2016-10-05 17:41:05 EDT
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
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>
Stack failed with status: Resource CREATE failed: resources: resources.Compute.Property error: resources.NetworkConfig.properties: Property ControlPlaneDefaultRoute not assigned
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.
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.