Bug 1378969

Summary: Managment network not deployed depending on order of templates included
Product: Red Hat OpenStack Reporter: Dan Sneddon <dsneddon>
Component: openstack-tripleo-heat-templatesAssignee: Jiri Stransky <jstransk>
Status: CLOSED NOTABUG QA Contact: Arik Chernetsky <achernet>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 10.0 (Newton)CC: mburns, rhel-osp-director-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-23 17:49:48 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:

Description Dan Sneddon 2016-09-23 17:15:56 UTC 
Description of problem:
When deploying network isolation with the management network, the management network will not be installed in network-isolation.yaml is included after network-environment.yaml.

Version-Release number of selected component (if applicable):
OSP 10 puddles (as of 2016/9/23)

How reproducible:
100%

Steps to Reproduce:
1. Run openstack overcloud deploy but include network-isolation.yaml last
2.
3.

Actual results:
The management network is not deployed.

Expected results:
The management network should be deployed.

Additional info:
This is fixed by patch at https://review.openstack.org/#/c/333048/ but that patch doesn't seem to be included in the latest OSP 10 puddles. I will submit a cherry-pick to make sure this change gets included.
Comment 1 Dan Sneddon 2016-09-23 17:49:48 UTC 
This bug was opened in error, the change has already been merged to the OSP 10 codebase.