Description of problem:
When you run "openstack overcloud node delete" it starts a stack update in Heat in the background then drops to the CLI. This could cause stack update collisions if you run another overcloud command immediately after. For example, run "openstack overcloud node delete" then run "openstack overcloud deploy" immediately after.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run "openstack overcloud node delete" and wait to be dropped to the command line
2. Run "openstack overcloud deploy" immediately after
3. Wait for a bit,then run "heat stack-list --show-nested" to see stack with status of "UPDATE_FAILED"
Stack update collisions
Maybe the same behavior as "openstack overcloud deploy" i.e. don't drop the the CLI, but instead show a log of the processes occurring.
I've documented where applicable to wait until the "openstack overcloud node delete" completes, but this might be a good RFE as a safety feature.
+1 It's odd when all the other cmds don't drop back into the cmd line until operation is complete.
There seems to already be work on-going to resolve this upstream. I'm updating the bug to match that information and will help with reviews as I can upstream. Brad, please let me know if this isn't ok or it turns out I misunderstood something. Thank you!
Patches merged upstream.
Checking the current puddle, the fix seems to be present. Updating NVR (hopefully correctly!) and component.
Verified. Deleted a compute node and saw that the workflow env was updated with the new counter.
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.