Description of problem: When deleting overcloud nodes, nodes are deleted *before* RHELUnregistrationDeployment resource is being deleted. Then RHELUnregistrationDeployment is stuck in DELETE_IN_PROGRESS and overcloud stack is stuck in UPDATE_IN_PROGRESS. Steven found out the root cause of the problem: RHELUnregistrationDeployment uses ComputeNodesPostDeployment. And scale-down is treated as an update, so ComputeNodesPostDeployment is updated *after* the Compute ResourceGroup has been resized. Version-Release number of selected component (if applicable): openstack-tripleo-heat-templates-0.8.6-64.el7ost.noarch Steps to Reproduce: 1. openstack overcloud deploy --templates --rhel-reg --reg-method portal --reg-org xxx --reg-activation-key 'key' --compute-scale 2 2. openstack overcloud node delete --templates --stack overcloud 86894343-a032-45f2-a619-122a23a3d5ba Actual results: Overcloud stack remains in UPDATE_IN_PROGRESS. Expected results: Stack update is completed.
upstream patche from Steven: https://review.openstack.org/#/c/227226/
upstream patches: https://review.openstack.org/227226 https://review.openstack.org/227225 https://review.openstack.org/229847
Verified: Environment: python-rdomanager-oscplugin-0.0.10-8.el7ost.noarch openstack-tripleo-heat-templates-0.8.6-71.el7ost.noarch Deployed with: 1. openstack overcloud deploy --templates --control-scale 3 --compute-scale 1 --ceph-storage-scale 0 -e <yaml files> --ntp-server X.X.X.X --timeout 90 --compute-flavor compute --control-flavor control -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml --rhel-reg --reg-method portal --reg-org <ID> --reg-activation-key '<key>' 2. Remobed a node with: openstack overcloud node delete --templates --stack overcloud 566f7a94-802a-43f9-9ba1-ff544884b1c7 Resulted in: +--------------------------------------+------------+-----------------+----------------------+ | id | stack_name | stack_status | creation_time | +--------------------------------------+------------+-----------------+----------------------+ | 8291d6ae-755c-4e63-a332-ed2623472a38 | overcloud | UPDATE_COMPLETE | 2015-10-01T18:57:56Z | +--------------------------------------+------------+-----------------+----------------------+
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/RHSA-2015:1862