Bug 1301549 - [RFE][UX] validate that there are no duplicate IPs as a result of bad templates in nic-configs
[RFE][UX] validate that there are no duplicate IPs as a result of bad templat...
Status: ON_QA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-validations (Show other bugs)
8.0 (Liberty)
Unspecified Unspecified
high Severity high
: Upstream M3
: 12.0 (Pike)
Assigned To: Florian Fuchs
Ola Pavlenko
: FutureFeature, Triaged
Depends On:
Blocks: 1442136 1467895 1469882
  Show dependency treegraph
 
Reported: 2016-01-25 06:24 EST by Udi
Modified: 2017-07-18 13:29 EDT (History)
12 users (show)

See Also:
Fixed In Version: openstack-tripleo-validations-7.1.1-0.20170707121256.821b048.el7ost
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
OpenStack gerrit 341586 None None None 2017-05-31 06:58 EDT
Polarion Requirement RHELOSP-23806 None None None 2017-06-07 09:37 EDT

  None (edit)
Description Udi 2016-01-25 06:24:08 EST
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):
8.0 beta


How reproducible:
100%


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


Actual results:
Deployment hangs for 4 hours and fails without a clear error message


Expected results:
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.
Comment 3 Mike Burns 2016-04-07 17:03:37 EDT
This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.
Comment 5 Ola Pavlenko 2016-12-12 09:37:01 EST
Potential candidate for M-3
Comment 10 Jason E. Rist 2017-07-06 18:51:37 EDT
Requesting M3Approved, this just needs a +A from cores.  Low impact, high need.
Comment 11 Jason E. Rist 2017-07-06 19:11:19 EDT
Actually it was just merged.

Note You need to log in before you can comment on or make changes to this bug.