If an exception was raised in delete_stack when deleting a nested stack,
the parent stack would never hear about it because we were accidentally
using cast() instead of call() to do the stack delete. This meant the
parent resource would remain DELETE_IN_PROGRESS until timeout when the
nested stack had already failed and raised an exception.
In the case of bug 1499669, the exception being missed was
StopActionFailed.
Change-Id: I039eb8f6c6a262653c1e9edc8173e5680d81e31b
Partial-Bug: #1499669
(cherry picked from commit e5cec71e52c3fed0ffb4385990758db8ebf367da)
Reviewed: https:/ /review. openstack. org/374846 /git.openstack. org/cgit/ openstack/ heat/commit/ ?id=adae45d7626 8eb57bf94600a40 4aa56d9769ca9c
Committed: https:/
Submitter: Jenkins
Branch: stable/mitaka
commit adae45d76268eb5 7bf94600a404aa5 6d9769ca9c
Author: Zane Bitter <email address hidden>
Date: Wed Sep 21 18:37:04 2016 -0400
Don't use cast() to do StackResource delete
If an exception was raised in delete_stack when deleting a nested stack,
the parent stack would never hear about it because we were accidentally
using cast() instead of call() to do the stack delete. This meant the
parent resource would remain DELETE_IN_PROGRESS until timeout when the
nested stack had already failed and raised an exception.
In the case of bug 1499669, the exception being missed was ailed.
StopActionF
Change-Id: I039eb8f6c6a262 653c1e9edc8173e 5680d81e31b 0ffb4385990758d b8ebf367da)
Partial-Bug: #1499669
(cherry picked from commit e5cec71e52c3fed