rabi a544ce43dc Reset resource replaced_by field for rollback ... We seem to leave replaced_by field of a resource after rollback (if a stack cancel is issued before the replacement resource is added to the stack). This in turn results in the stack getting stuck in IN_PROGRESS for further updates. Change-Id: I3361ad90e303d24a16a943408fe0f6c406cf785f Co-Authored-By: Zane Bitter <zbitter@redhat.com> Task: #19582 Story: #2001974		2018-05-11 15:04:53 +05:30
..
api	Remove stack watch service	2018-01-28 09:35:05 +05:30
cloudinit	Validate that python3 is ready for loguserdata	2016-08-26 11:49:30 +00:00
cmd	Remove stack watch service	2018-01-28 09:35:05 +05:30
common	Merge "Docs: modernise links"	2018-04-27 11:36:18 +00:00
db	Merge "Remove db api and tables for CloudWatch"	2018-02-16 23:30:40 +00:00
engine	Reset resource replaced_by field for rollback	2018-05-11 15:04:53 +05:30
hacking	Restrict use of iteritems, iterkeys and itervalues	2016-03-23 10:05:54 +00:00
httpd	Remove CloudWatch API	2018-01-28 09:11:17 +05:30
locale	Imported Translations from Zanata	2018-03-12 06:43:23 +00:00
objects	Remove stack watch service	2018-01-28 09:35:05 +05:30
policies	Remove CloudWatch API	2018-01-28 09:11:17 +05:30
rpc	Remove stack watch service	2018-01-28 09:35:05 +05:30
scaling	Merge "Eliminate nested stack loading in InstanceGroup/ASG scaling"	2018-04-02 04:35:47 +00:00
tests	Reset resource replaced_by field for rollback	2018-05-11 15:04:53 +05:30
__init__.py	Make import of oslo libraries namespaceless	2015-02-18 22:54:10 +01:00
version.py	…