Description of problem:
If both network-management.yaml and newtork-isolation.yaml are included in the deployment command-line, and the network-isolation.yaml file is included later, then it overrides the management network, causing the Control Plane IP to appear where the Management IP should.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. openstack overcloud deploy --templates -e /path/to/network-management.yaml -e /path/to/network-isolation.yaml
The first file enables the Management network, and the second disables it.
The management network should be enabled.
Since the Management nework is disabled by default, there is no reason to include it in the network-isolation.yaml file.
Fix submitted upstream: https://review.openstack.org/#/c/333048
This still hasn't landed in the stable/mitaka branch as far as I know.
Could you backport it?
(In reply to Thierry Vignaud from comment #3)
> This still hasn't landed in the stable/mitaka branch as far as I know.
> Could you backport it?
This patch will be backported to stable/mitaka once it has been merged in master. We don't do backports before the originating patch is merged, because it causes issues when we backport and then the original patch is revised.
This patch was merged to tripleo-heat-templates today, so I created a backport to stable/mitaka here:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.