Bug 1258967
Summary: | Parameters in stack-show are not updated after a failed update | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Zane Bitter <zbitter> | |
Component: | openstack-heat | Assignee: | Zane Bitter <zbitter> | |
Status: | CLOSED ERRATA | QA Contact: | Amit Ugol <augol> | |
Severity: | unspecified | Docs Contact: | ||
Priority: | high | |||
Version: | 7.0 (Kilo) | CC: | ddomingo, mburns, pablo.iranzo, sbaker, shardy, yeylon, zbitter | |
Target Milestone: | z2 | Keywords: | Triaged, ZStream | |
Target Release: | 7.0 (Kilo) | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | openstack-heat-2015.1.1-1.el7ost | Doc Type: | Bug Fix | |
Doc Text: |
Previously, when a stack update failed the Orchestration service continued to store the old parameter values instead of the ones supplied with the failed update attempt. Whenever this occurred, the Orchestration service incorrectly showed the parameter values from the last successful update. If the parameter schema of the template changed, attempting to show the failed stack sometimes resulted in an error.
With this release, the Orchestration service now updates stored parameter values with new values during and after a failed update. As a result, when showing a stack, the parameter values will be the last ones supplied (as expected) even after a failed update.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1263091 (view as bug list) | Environment: | ||
Last Closed: | 2015-10-08 12:20:57 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1255910, 1263091 |
Description
Zane Bitter
2015-09-01 15:42:57 UTC
both required, required+default values and unused parameters are being updated to show the most recent update attempt. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2015:1865 |