Bug 1469542
Summary: | heat api fails to list resources due to wrong value of needed_by in undercloud | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Jaison Raju <jraju> | |
Component: | openstack-heat | Assignee: | Zane Bitter <zbitter> | |
Status: | CLOSED ERRATA | QA Contact: | Ronnie Rasouli <rrasouli> | |
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | 11.0 (Ocata) | CC: | ddomingo, jjoyce, jraju, mburns, nshetty, ramishra, rhel-osp-director-maint, sbaker, shardy, srevivo, therve, zbitter | |
Target Milestone: | z3 | Keywords: | TestOnly, Triaged, ZStream | |
Target Release: | 11.0 (Ocata) | |||
Hardware: | All | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | openstack-heat-8.0.3-1.el7ost | Doc Type: | Bug Fix | |
Doc Text: |
If a stack was created using a version of Heat from RHEL-OSP 7 or earlier, listing resources for the stack would fail beginning with the Heat version from OSP 10, with an error calculating the 'required_by' data. In addition, even for stacks created with later versions of Heat the 'required_by' field was not populated, unless the convergence_engine option was enabled (which is the default starting with OSP 10) at the time the stack was created. Heat now correctly populates the 'required_by' field without error.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1477891 (view as bug list) | Environment: | ||
Last Closed: | 2017-10-31 17:42: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: | 1477891 |
Description
Jaison Raju
2017-07-11 13:17:33 UTC
Having null in the database is not a problem per se. The problem is that we're hitting a code path that we're not intending to hit unless the value has been updated to []. That said, updating the database to contain [] instead of null would work, and wouldn't have any negative consequences. 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-2017:3099 |