Zane Bitter b0d7ffadc3 Pre-empt in-progress nested stack updates on new update ... If the parent resource of a nested stack is locked due to an IN_PROGRESS update, cancel the nested stack update (which will result in the parent resource being marked FAILED and releasing the lock so that the new traversal can begin acting on it). This effectively results in the model for simultaneous updates in a single stack (that we wait for in-progress work when it would conflict, but otherwise don't delay starting a new update) being extended recursivey down through nested stacks. Change-Id: I5f14453ebab75d89672c6eea12de46d48a5147f3 Task: 17760		2019-10-23 21:22:23 -04:00
..
aws	Fix coverity check FORWARD_NULL error	2019-08-06 08:53:42 +08:00
openstack	Don't mark snapshot complete while task in progress	2019-10-09 11:19:35 +08:00
__init__.py	Log missing clients as WARNING instead of ERROR	2016-08-16 16:27:55 -05:00
alarm_base.py	Update incorrect timezone description	2017-09-19 13:46:32 +08:00
scheduler_hints.py	Fix path_in_stack for scheduler hints	2016-08-05 10:21:10 +00:00
server_base.py	Add dedicated auth endpoint config for servers	2019-07-12 13:50:38 +00:00
signal_responder.py	Add dedicated auth endpoint config for servers	2019-07-12 13:50:38 +00:00
stack_resource.py	Pre-empt in-progress nested stack updates on new update	2019-10-23 21:22:23 -04:00
stack_user.py	Remove log translations	2017-03-25 17:11:50 +08:00
template_resource.py	Revert "Use OutputDefinition to generate attributes schema"	2018-11-28 12:13:58 -05:00
volume_base.py	Check for server in attachements when checking for detach complete	2018-09-24 17:28:52 +05:30
wait_condition.py	Always use string ID for WaitConditionHandle signals	2018-02-09 20:20:22 -05:00