Red Hat Bugzilla – Bug 1266102
overcloud node delete after failure can remove too many nodes
Last modified: 2015-12-21 11:55:29 EST
Copied from a comment on bug 1255910:
It turns out that under certain circumstances BZ 1258967 is not sufficient fix for this issue [bug 1255910]:
- if a user tried to delete a node and this operation failed before, then using ComputeCount parameter for computing new node count is insufficient.
An upstream patch which counts new node count from actual nodes in ResourceGroup is here:
I tried to scale up form 1 compute to 2, and the operation failed (nova returned "Message: Unknown, Code: Unknown"). I then used "nova delete" to delete the failed node. In stack-show I still see ComputeCount = 2, but at least it didn't delete all the computes there are.
How do I bring the stack to a consistent state with ComputeCount = 1? How to verify this bug? Thanks.
Use the "openstack overcloud node delete" command to remove it from Heat's model.
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.