Bug 1378969 - Managment network not deployed depending on order of templates included
Summary: Managment network not deployed depending on order of templates included
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Jiri Stransky
QA Contact: Arik Chernetsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-23 17:15 UTC by Dan Sneddon
Modified: 2016-09-23 17:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-23 17:49:48 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.