Empty data can be cause of some errors during deleting backup stack
Bug #1496909 reported by
Sergey Kraynev
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Heat |
Fix Released
|
Medium
|
Sergey Kraynev | ||
| Kilo |
Fix Released
|
Medium
|
Angus Salkeld | ||
Bug Description
In case when UpdateReplace failed we copy backup resource properties and resource_id [1].
However some resource can contain important (for example used during deletion) information in data.
To avoid potential issues, when data is empty and we can not correctly process it, let's copy resource data from backup resource too.
[1] https:/
| Changed in heat: | |
| status: | Triaged → In Progress |
| tags: |
added: kilo-backport-potential removed: juno-backport-potential |
| tags: | removed: kilo-backport-potential |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to heat (master) | #1 |
| Changed in heat: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to heat (stable/kilo) | #2 |
| Changed in heat: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to heat (stable/kilo) | #3 |
| Changed in heat: | |
| milestone: | liberty-rc1 → 5.0.0 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 71268bea28c8959
Author: Sergey Kraynev <email address hidden>
Date: Mon Sep 7 08:55:55 2015 -0400
Copy resource data in _delete_
Currently during deleting backup stack we copy properties and
resource id from new to backup resource and conversely. Same thing
should be done for resource data, because it may ve also used in some
deleting operations.
Change-Id: Id121cf9eb391ad
Closes-Bug: #1496909