Bug 1299257
Summary: | heat API: actions->check removes stack output values. | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Matt Flusche <mflusche> | |
Component: | openstack-heat | Assignee: | Thomas Hervé <therve> | |
Status: | CLOSED ERRATA | QA Contact: | Amit Ugol <augol> | |
Severity: | urgent | Docs Contact: | ||
Priority: | urgent | |||
Version: | 7.0 (Kilo) | CC: | jcoufal, mburns, ochalups, rhel-osp-director-maint, sbaker, shardy, ssainkar, therve, yeylon, zbitter | |
Target Milestone: | z4 | Keywords: | ZStream | |
Target Release: | 7.0 (Kilo) | |||
Hardware: | Unspecified | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | openstack-heat-2015.1.2-8.el7ost | Doc Type: | Bug Fix | |
Doc Text: |
Previously, using the heat API actions > check call removed the output values from existing heat stack. This behaviour was observed with the CLI (heat action-check <heat-stack>) and dashboard (heat "Check Stack" button). This broke stack updates and other operations depending on stack output values after this operation was executed.
This patch gets attribute instead of return None if resource is in SNAPSHOT or CHECK action which resolves the issue.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1299912 (view as bug list) | Environment: | ||
Last Closed: | 2016-02-18 16:43:01 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: | 1299912 |
Description
Matt Flusche
2016-01-17 22:37:22 UTC
I think I identified the bug as https://bugs.launchpad.net/heat/+bug/1505054 I started the backporting process here: https://review.openstack.org/#/c/268957/ using the steps from the original message, this seems to be working well now. 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://rhn.redhat.com/errata/RHSA-2016-0266.html |