Red Hat Bugzilla – Bug 1301549
[RFE][UX] validate that there are no duplicate IPs as a result of bad templates in nic-configs
Last modified: 2017-07-18 13:29:10 EDT
Description of problem:
I edited my network-environment.yaml and changed all storage-mgmt ports and networks to noop. I mapped storage-mgmt to storage as well and tried to deploy. The deployment hanged and timed out after 4 hours without giving me a clue as to the cause. It turned out that I still had references to the storage-mgmt vlan and IP in the nic-configs, and the ceph node got a duplicate IP for the ctlplane on 2 different nics.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set some ports and networks to noop, and then still define them on a nic which is not the one that's supposed to be for the ctlplane
Deployment hangs for 4 hours and fails without a clear error message
This situation should be detectable. Any config that will result in duplicate IPs should be stopped before the deployment starts, and the user should get an informative error message.
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
Potential candidate for M-3
Requesting M3Approved, this just needs a +A from cores. Low impact, high need.
Actually it was just merged.