Bug 1234108 – In this example, there is no way to know the id of the parent resource to use in "heat resource-show"

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1234108 - In this example, there is no way to know the id of the parent resource to use in "heat resource-show"

Summary:	In this example, there is no way to know the id of the parent resource to use...

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat OpenStack
Classification:	Red Hat
Component:	python-heatclient (Show other bugs)
Sub Component:
Version:	7.0 (Kilo)
Hardware:	Unspecified Unspecified

Priority	unspecified Severity medium
Target Milestone:	beta
Target Release:	8.0 (Liberty)
Assigned To:	Steve Baker
QA Contact:	Shai Revivo
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2015-06-21 08:24 EDT by Udi
Modified:	2016-04-26 16:31 EDT (History)
CC List:	8 users (show)

See Also:
Fixed In Version:	python-heatclient-0.8.0-1.el7ost
Doc Type:	Bug Fix
Doc Text:	Previously, the output of the "heat resource-list --nested-depth ..." command contained a column called "parent_resource"; however, the output did not include the information required to run a subsequent "heat resource-show ..." command. With this update, the output of the "heat resource-list --nested-depth ..." command includes a column called "stack_name", which provides the values to use in a "heat resource-show [stack_name] [resource_name]" call.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2016-04-07 17:02:04 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Launchpad	1467332	None	None	None	Never
Red Hat Product Errata	RHEA-2016:0603	normal	SHIPPED_LIVE	Red Hat OpenStack Platform 8 Enhancement Advisory	2016-04-07 20:53:53 EDT

Groups: None (edit)

Description Udi 2015-06-21 08:24:54 EDT

Description of problem:
Here is an example of "heat resource-list" with a recursive depth of 5 that shows all the failed resources in the stack:

$ heat resource-list -n 5 overcloud |grep FAIL
| Compute     | 647fdedb-... | OS::Heat::ResourceGroup | CREATE_FAILED | ... |            |
| Controller  | f7bd7fff-... | OS::Heat::ResourceGroup | CREATE_FAILED | ... |            |
| 0           | a37df3f4-... | Tuskar::Controller-1    | CREATE_FAILED | ... | Controller |
| 0           | e3da137d-... | Tuskar::Compute-1       | CREATE_FAILED | ... | Compute    |
| Controller  | 53efb90d-... | OS::Nova::Server        | CREATE_FAILED | ... | 0          |
| NovaCompute | 4f1d6f76-... | OS::Nova::Server        | CREATE_FAILED | ... | 0          |

Note that in this example, the last 2 resources have a parent resource called "0". I can see two resources called "0" which are in FAILED state, and I have no way to determine (except by trial and error) which parent is the parent of which child.

The syntax for the heat resource-show command is very inconsistent. It requires 2 parameters to be passed:
1) The resource id of the parent resource (passing the resource name won't work)
2) The name of the child resource to show (if you try to pass an id here it won't work)


Expected results:
You'd expect the resource-show command to take the stack name and the resource id to show. There is no need to pass the parent resource id, and as it stands today the command doesn't require you to pass the stack name at all (very wierd!!!).

Comment 3 Steve Baker 2015-06-21 18:24:18 EDT

I've added an upstream bug to track this. Feel free to comment there too.

Comment 4 Jon Schlueter 2016-01-28 09:33:00 EST

moving to modifed with NVR, upstream launchpad indicates fix was included in version prior to build included in OSP 8

Comment 6 Udi 2016-02-28 04:02:30 EST

Verified in:
python-heatclient-0.8.0-1.el7ost.noarch
openstack-heat-engine-5.0.1-1.el7ost.noarch
openstack-heat-common-5.0.1-1.el7ost.noarch

Comment 8 errata-xmlrpc 2016-04-07 17:02:04 EDT

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/RHEA-2016-0603.html

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