diff options
author | ramishra <ramishra@redhat.com> | 2021-04-01 10:19:31 +0530 |
---|---|---|
committer | ramishra <ramishra@redhat.com> | 2021-04-01 19:39:58 +0530 |
commit | bfbaab107d709c37548a22239b952c6221b9ac85 (patch) | |
tree | c87b8594c79e1d240a4e7c42d2016f528a385d90 /heat/objects | |
parent | 6ff0dc2e19ddf3a3447810f8a55b29d9bec52136 (diff) | |
download | heat-bfbaab107d709c37548a22239b952c6221b9ac85.tar.gz |
Don't update status for replaced resource
With I04e7ad90944c2d03ce0e59ba16af9d60d6e01222 we allowed
update of previously-existing resource if replacement
creation has failed during last update. However, we force
update the status of the existing resource to 'COMPLETE'.
Therefore, in the next update if properties/type has not
changed for the resource it won't try to update/replace
the previously existing resource resulting in false positive
of stack updated successfully.
Task: 42194
Change-Id: Icc90a921ec67e49aec2c4acfad72235c57c78421
Diffstat (limited to 'heat/objects')
-rw-r--r-- | heat/objects/resource.py | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/heat/objects/resource.py b/heat/objects/resource.py index c99e572dc..c5aacd4fc 100644 --- a/heat/objects/resource.py +++ b/heat/objects/resource.py @@ -200,12 +200,11 @@ class Resource( @classmethod def replacement(cls, context, - existing_res_id, existing_res_values, + existing_res_id, new_res_values, atomic_key=0, expected_engine_id=None): replacement = db_api.resource_create_replacement(context, existing_res_id, - existing_res_values, new_res_values, atomic_key, expected_engine_id) |