Bug 1506715 - Error getting outputs from nested stack renders stack unusable
Summary: Error getting outputs from nested stack renders stack unusable
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-heat
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 12.0 (Pike)
Assignee: Zane Bitter
QA Contact: Ronnie Rasouli
Depends On:
TreeView+ depends on / blocked
Reported: 2017-10-26 15:59 UTC by Zane Bitter
Modified: 2018-02-05 19:15 UTC (History)
6 users (show)

Fixed In Version: openstack-heat-9.0.1-2.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-12-13 22:18:18 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Launchpad 1712280 0 None None None 2017-10-26 15:59:43 UTC
OpenStack gerrit 515454 0 None None None 2017-10-26 16:00:29 UTC
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Description Zane Bitter 2017-10-26 15:59:43 UTC
In Pike, Heat loads any attribute values required to serve an API call at the beginning of the call. If an exception occurs loading any of these values, then the API call will fail.

An error in an output of a nested stack causes an exception to be raised in the parent stack if that output is referenced as an attribute of the parent resource. Thus, once this occurs showing the root stack with output resolution will fail, as will operations like stack updates.

Comment 2 Zane Bitter 2017-11-01 14:00:46 UTC
Backport is merged to stable/pike upstream.

Comment 4 Ronnie Rasouli 2017-11-15 15:07:26 UTC
verified by heat_integrationtests.functional.test_stack_outputs, tested passed

Comment 7 errata-xmlrpc 2017-12-13 22:18:18 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.