tripleo-heat-templates: Including the nework-isolation.yaml file after network-management.yaml disables the Management network.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Undecided
|
Dan Sneddon | ||
Mitaka |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Description of problem:
If both network-
Version-Release number of selected component (if applicable):
OSP-Director 8.0
How reproducible:
100%
Steps to Reproduce:
1. openstack overcloud deploy --templates -e /path/to/
Actual results:
The first file enables the Management network, and the second disables it.
Expected results:
The management network should be enabled.
Additional info:
Since the Management nework is disabled by default, there is no reason to include it in the network-
Changed in serposcope: | |
assignee: | nobody → Dan Sneddon (dsneddon) |
status: | New → In Progress |
affects: | serposcope → tripleo |
Reviewed: https:/ /review. openstack. org/333048 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=bf41f8f358f c2ae7dde1f7be94 aa9027a27db09d
Committed: https:/
Submitter: Jenkins
Branch: master
commit bf41f8f358fc2ae 7dde1f7be94aa90 27a27db09d
Author: Dan Sneddon <email address hidden>
Date: Wed Jun 22 14:50:23 2016 -0700
Fix network- isolation. yaml to stop clobbering Management net
The network- isolation. yaml file explicitly set the Management management. yaml was isolation. yaml.
network to None and the ports to noop.yaml. This resulted in the
Management network being disabled if network-
included before network-
These changes comment out the Management declarations to show the management. yaml may be included.
default, and mention that network-
Since the Management network is disabled by default, it isn't
necessary to noop it here. This change also places the Redis VIP
in a more logical place next to the controller ports.
Change-Id: I50a71b3ddf77bd a2d213821da5e42 60b503a6cb7
Fixes-bug: 1602283