Sirushti Murugesan 8f31346c1c Wait for the stack lock to be released ... Sometimes, when trying to update a stack in a *_COMPLETE/FAILED status, it can fail since the stack lock is not released yet. As a short-term workaround, I've put in place an ugly hack that will simply retry the update if the operation failed because of the stack lock. The downside of this is that we can't now add functional tests which will test updates on Stack Lock itself since we now simply just ignore the HTTPConflict Exception on updates. I couldn't think of another solution that doesn't include a giant refactoring that will solve this problem. PS: Convergence doesn't have the notion of a Stack-Lock, so that should take care of this by default. Partially-Closes Bug: #1450314 Change-Id: Ib1a9d5c425285ebcffcb9ff8a362a56fd8f3574a		2015-05-04 14:58:18 +05:30
..
test_resources	test_resource for functional tests	2015-04-08 11:09:46 +05:30
__init__.py	Support classes for heat integration tests	2014-09-24 09:02:20 +12:00
clients.py	Use oslo.log for heat_integrationtests	2015-03-17 17:36:56 +13:00
config.py	Add minimal_instance_type config option	2015-03-23 14:02:46 +00:00
exceptions.py	Support classes for heat integration tests	2014-09-24 09:02:20 +12:00
remote_client.py	Update urllib/httplib/cStringIO to use six.moves	2015-04-23 19:45:36 +05:30
test.py	Wait for the stack lock to be released	2015-05-04 14:58:18 +05:30