heat/heat
Zane Bitter 5681e237c5 Avoid creating new resource with old template
If a traversal is interrupted by a fresh update before a particular
resource is created, then the resource is left stored in the DB with the
old template ID. While an update always uses the new template, a create
assumes that the template ID in the DB is correct. Since the resource has
never been created, the new traversal will create it using the old
template.

To resolve this, detect the case where the resource has not been created
yet and we are about to create it and the traversal ID is still current,
and always use the new resource definition in that case.

Change-Id: Ifa0ce9e1e08f86b30df00d92488301ea05b45b14
Closes-Bug: #1663745
2017-06-05 23:14:19 -04:00
..
api Remove log translations 2017-03-25 17:11:50 +08:00
cloudinit Validate that python3 is ready for loguserdata 2016-08-26 11:49:30 +00:00
cmd Remove log translations 2017-03-25 17:11:50 +08:00
common Fix logging in devstack 2017-06-02 15:20:57 +00:00
db Merge "Don't fetch stack before update in stack_update()" 2017-06-05 15:51:48 +00:00
engine Avoid creating new resource with old template 2017-06-05 23:14:19 -04:00
hacking Restrict use of iteritems, iterkeys and itervalues 2016-03-23 10:05:54 +00:00
httpd Remove log translations 2017-03-25 17:11:50 +08:00
locale Imported Translations from Zanata 2017-05-02 10:32:02 +00:00
objects Merge "Load "lighter" db resources when appropriate" 2017-06-05 09:50:38 +00:00
rpc Merge "Use exception_filter in RPC client" 2017-03-29 13:46:53 +00:00
scaling Remove log translations 2017-03-25 17:11:50 +08:00
tests Avoid creating new resource with old template 2017-06-05 23:14:19 -04:00
__init__.py Make import of oslo libraries namespaceless 2015-02-18 22:54:10 +01:00
version.py Make the first line of every file consistent. 2014-03-04 09:03:04 -06:00