Version:
OSP10 (Newton)
heat-cfntools-1.3.0-2.el7ost.noarch
openstack-heat-api-7.0.6-1.el7ost.noarch
openstack-heat-api-cfn-7.0.6-1.el7ost.noarch
openstack-heat-api-cloudwatch-7.0.6-1.el7ost.noarch
openstack-heat-common-7.0.6-1.el7ost.noarch
openstack-heat-engine-7.0.6-1.el7ost.noarch
openstack-heat-templates-0-0.14.1e6015dgit.el7ost.noarch
openstack-tripleo-heat-templates-5.3.3-1.el7ost.noarch
openstack-tripleo-heat-templates-compat-2.0.0-58.el7ost.noarch
puppet-heat-9.5.0-2.el7ost.noarch
python-heat-agent-0-0.14.1e6015dgit.el7ost.noarch
python-heat-tests-7.0.6-1.el7ost.noarch
python-heatclient-1.5.2-1.el7ost.noarch
How to reproduce:
0) Scale out with additional node (for example index 10)
1) Node with index 10 is created successfully in Heat database
2) Node with index 10 is assigned instance_uuid in Nova
Now the problem appears that for example: there is HW issue. the node can't boot to disk.
3) Node fails with ERROR in Nova state
4) Try to remove node with 'overcloud node delete ... [instance_uuid]'
5) Heat removes the last node instead
Actual results:
Heat removes the last node instead
Expected results:
Heat should remove the node specified and perform update
We guess this behavior is because the stack is already in FAILED state.
> We guess this behavior is because the stack is already in FAILED state.
Yes, heat would try to _replace_ all FAILED resources/nodes by default with an stack update.
Assuming that the a node is in FAILED state, I would also expect it to remove the node blacklisted (03c28a44-979b-4ed2-9463-04661df11570) and try replace the node in FAILED state, both.
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-2018:1597