Bug 1663545 - [rhos-prio] Issues recovering after scaling out to more nodes than available
Summary: [rhos-prio] Issues recovering after scaling out to more nodes than available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-tripleoclient
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ---
: 10.0 (Newton)
Assignee: Rabi Mishra
QA Contact: Victor Voronkov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-04 19:48 UTC by rosingh
Modified: 2019-06-12 16:47 UTC (History)
13 users (show)

Fixed In Version: python-tripleoclient-5.4.6-2.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-30 16:58:51 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 4217151 0 Troubleshoot None Deployment fails immediately with "Not enough nodes" 2019-06-12 16:47:53 UTC
Red Hat Product Errata RHBA-2019:0921 0 None None None 2019-04-30 16:59:10 UTC

Description rosingh 2019-01-04 19:48:34 UTC 
Description of problem:
In the process of running a stack deploy on a site with 96 BL460C blades ("Compute" blades). The customer had the number of computeV2 nodes set to 96, when in reality, they have 0 available at this time  and the stack update failed. 
However, when they set the number of computeV2 nodes to the correct number of 0, the templates fail deploy due to:
Not enough nodes - available: 99, requested: 195

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 15 Victor Voronkov 2019-04-02 16:04:32 UTC 
Verified on compose 2019-03-26.1 that with wrong ComputeCount update fails and after fixing to valid avaliable compute host amount and rerunning deploy script, overcloud stack is updated successfully
Comment 17 errata-xmlrpc 2019-04-30 16:58:51 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/RHBA-2019:0921
Note You need to log in before you can comment on or make changes to this bug.