Zane Bitter a96d89b200 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 StopActionFailed. Change-Id: I039eb8f6c6a262653c1e9edc8173e5680d81e31b Partial-Bug: #1499669 (cherry picked from commit e5cec71e52)		2016-09-22 10:05:59 -04:00
..
aws	Move NoActionRequired exception back where it belongs	2016-08-18 12:57:54 -04:00
openstack	Fix cancel update for nova server with defined port	2016-09-21 08:50:56 +05:30
__init__.py	Log missing clients as WARNING instead of ERROR	2016-08-16 16:27:55 -05:00
alarm_base.py	Migrate to aodh for OS::Ceilometer::Alarm	2016-06-29 02:50:27 +00:00
scheduler_hints.py	Fix path_in_stack for scheduler hints	2016-08-05 10:21:10 +00:00
signal_responder.py	Use Zaqar signed URLs in software deployment	2016-06-21 10:01:49 +02:00
stack_resource.py	Don't use cast() to do StackResource delete	2016-09-22 10:05:59 -04:00
stack_user.py	Migrate to keystoneauth	2016-09-06 10:07:22 +05:30
template_resource.py	Handle outputs with an OutputDefinition class	2016-09-09 16:14:16 -04:00
volume_base.py	Merge "Deal with cinder-backup service absent"	2016-08-18 17:32:03 +00:00
wait_condition.py	Refactor BaseWaitConditionHandle._metadata_format_ok()	2016-03-24 02:53:34 -04:00