Crag Wolfe 2ec2d5a973 Allow retries when resource acquires lock ... Previously, if an update or delete on a resource is initiated concurrently with another action (e.g. a metadata update as the result of a resource signal) it may end up failing with exception.UpdateInProgress because its view of the resource's atomic_key is stale. Now, we retry, rereading the resource's atomic_key from the db if needed, up to cfg.CONF.action_retry_limit times. Change-Id: I4cfa6f691fe916c0d605a712028b88f61ebab4d9 Partial-Bug: #1675286		2017-05-03 18:24:46 -04:00
..
templates	Merge "Do not set the mime-type for userdata"	2016-12-15 03:10:04 +00:00
__init__.py	Move test_server_cfn_init from tempest to heat	2014-10-07 12:50:32 +13:00
scenario_base.py	Use minimal image wherever possible	2016-09-29 12:18:17 +05:30
test_aodh_alarm.py	Allow retries when resource acquires lock	2017-05-03 18:24:46 -04:00
test_autoscaling_lb.py	Wait for the policy to be done in tests	2017-04-10 23:44:26 +02:00
test_autoscaling_lbv2.py	Wait for the policy to be done in tests	2017-04-10 23:44:26 +02:00
test_server_cfn_init.py	Use minimal image wherever possible	2016-09-29 12:18:17 +05:30
test_server_signal.py	Do not set the mime-type for userdata	2016-11-25 14:47:53 +08:00
test_server_software_config.py	Use more specific asserts in tests	2016-11-22 08:12:35 +01:00
test_volumes.py	Don't use hardcoded flavors in tests	2016-12-06 12:14:18 +05:30