|Summary:||Warn if there are not enough IPs in the pool (otherwise deployment hangs)|
|Product:||Red Hat OpenStack||Reporter:||Udi <ukalifon>|
|Component:||openstack-tripleo-validations||Assignee:||Ana Krivokapic <akrivoka>|
|Status:||CLOSED ERRATA||QA Contact:||nlevinki <nlevinki>|
|Version:||8.0 (Liberty)||CC:||akrivoka, apannu, augol, beth.white, dbecker, dsneddon, dtantsur, flfuchs, gchamoul, jcoufal, jjoyce, jschluet, mburns, morazi, rhel-osp-director-maint, rhos-flags, sclewis, slinaber, tvignaud|
|Target Release:||13.0 (Queens)|
|Fixed In Version:||openstack-tripleo-validations-8.4.0-1.el7ost||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2018-06-27 13:26:26 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Udi 2016-03-24 16:41:22 UTC
Description of problem: When using the static IP allocation feature, no validations are run to see if there are enough IPs in the pool for the requested number of nodes. The deployment simply hangs until it times out. Version-Release number of selected component (if applicable): python-tripleoclient-0.3.1-1.el7ost.noarch openstack-tripleo-heat-templates-0.8.12-1.el7ost.noarch How reproducible: 100 % Steps to Reproduce: 1. In your environment file, create an IP pool for the compute nodes, but make sure you won't have enough for them all. In this example there is only 1 IP: parameter_defaults: NovaComputeIPs: internal_api: - 10.35.191.100 2. Deploy with more nodes than the pool size Actual results: Deployment hangs Expected results: User should get a clear error right on the beginning of the deployment, that more IPs are needed in the pool. Deployment should be aborted and not even attempted.
Comment 2 Mike Burns 2016-04-07 21:36:02 UTC
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
Comment 3 Dan Sneddon 2016-10-14 14:38:50 UTC
While I think this BZ would be good to address, I think the fact that you need to have sufficient IP space in your allocation pools is well documented. I changed the topic of this BZ to indicate that is a feature request. I think this is best addressed with an addition to the tripleo-validations. I have added this BZ to the list of future enhancements to networking validations in tripleo-validations. I am setting the target to OSP 11 for now, although it isn't yet clear if this particular enhancement will be able to land in Ocata.
Comment 14 errata-xmlrpc 2018-06-27 13:26:26 UTC
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. https://access.redhat.com/errata/RHEA-2018:2086