e5cec71e52
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 |
||
---|---|---|
.. | ||
aws | ||
openstack | ||
__init__.py | ||
alarm_base.py | ||
scheduler_hints.py | ||
signal_responder.py | ||
stack_resource.py | ||
stack_user.py | ||
template_resource.py | ||
volume_base.py | ||
wait_condition.py |