Zane Bitter ce22b59b62 Revert "Hard delete backup stack after successful update." ... This reverts commit 7cf6e52cac. This change appears to be the cause of many Tempest test breakages. Prior to this a new raw_template entry was created in the database after an update, and the pointer to the new raw_template and the stack status were changed atomically. Now those two pieces of data are being updated separately... it seems like it is possible for the database to return the new version of the stack on one call followed by the old version of the template on another call. Tempest is observing the stack status change to UPDATE_COMPLETE but then still getting data from the old template when doing a resource list immediately after. Change-Id: Ieea739bc45dcc365ccb6f09d0e848e310d327134 Partial-Bug: #1370865		2014-10-06 16:46:55 -04:00
..
sqlalchemy	Revert "Hard delete backup stack after successful update."	2014-10-06 16:46:55 -04:00
__init__.py	Do not initialize anything during import phase	2013-04-24 10:03:06 -07:00
api.py	Revert "Hard delete backup stack after successful update."	2014-10-06 16:46:55 -04:00
sync.py	Switch heat resources & db & tests to oslo.i18n	2014-09-17 14:28:56 +08:00
utils.py	Sync latest oslo.db code	2014-04-11 10:48:46 +03:00