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:
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
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
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: