Bug 1424597
| Summary: | [backport] --format json doesn't work since python-heatclient 0.8.0 | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Zane Bitter <zbitter> |
| Component: | python-heatclient | Assignee: | Crag Wolfe <cwolfe> |
| Status: | CLOSED ERRATA | QA Contact: | Shai Revivo <srevivo> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 9.0 (Mitaka) | CC: | aguetta, augol, cwolfe, dcadzow, jruzicka, mburns, nlevinki, pablo.iranzo, rhel-osp-director-maint, samccann, shardy, srevivo, therve, zbitter |
| Target Milestone: | --- | Keywords: | FeatureBackport, Triaged, ZStream |
| Target Release: | 9.0 (Mitaka) | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | python-heatclient-1.2.0-2.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
Cause: When running the "heat output-show" command with the "--format json" option, only the output value was shown.
Consequence: This was a change in behavior from previous versions (prior to 0.8.0), where the entire output definition (including the output_value, but also the description) was shown. There was no longer any way to get all of the data returned by the underlying API with the command line.
Fix: The default format changes from "json" to "raw", but when the "json" format is selected the entire output data is shown.
Result: There is no change in the default behavior, but when the "--format json" option is passed all of the data returned by the underlying API is shown, not just the output value.
|
Story Points: | --- |
| Clone Of: | 1421683 | Environment: | |
| Last Closed: | 2017-06-14 15:45: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: | 1421683, 1424600 | ||
| Bug Blocks: | |||
|
Description
Zane Bitter
2017-02-17 18:22:32 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. https://access.redhat.com/errata/RHBA-2017:1460 |