If a stack update is cancelled while the update of a nested stack is being
processed, the nested stack update is no longer stopped since the
implementation changed in Kilo to use the RPC API to control nested stacks.
To alleviate this, use the RPC API to cancel the (nested) stack update when
the resource update is cancelled. This results in a rollback of the nested
stack, so if a subsequent attempt to roll back the ensted stack by doing a
stack update fails due to the rollback already being in progress, just
ignore the error and wait for the existing operation to complete.
Reviewed: https:/ /review. openstack. org/175606 /git.openstack. org/cgit/ openstack/ heat/commit/ ?id=ad4c00e672f dd2c1c8461d7e48 13dff4b093ae0f
Committed: https:/
Submitter: Jenkins
Branch: master
commit ad4c00e672fdd2c 1c8461d7e4813df f4b093ae0f
Author: Zane Bitter <email address hidden>
Date: Mon Apr 20 19:12:07 2015 -0400
Cancel nested stack updates when appropriate
If a stack update is cancelled while the update of a nested stack is being
processed, the nested stack update is no longer stopped since the
implementation changed in Kilo to use the RPC API to control nested stacks.
To alleviate this, use the RPC API to cancel the (nested) stack update when
the resource update is cancelled. This results in a rollback of the nested
stack, so if a subsequent attempt to roll back the ensted stack by doing a
stack update fails due to the rollback already being in progress, just
ignore the error and wait for the existing operation to complete.
Change-Id: I3eacf216194517 c995732a3f4de87 6551b70fe91
Closes-Bug: #1446252