RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1226653 - The usage message for "heat resource-show" is confusing and incorrect
Summary: The usage message for "heat resource-show" is confusing and incorrect
Keywords:
Status: CLOSED EOL
Alias: None
Product: RDO
Classification: Community
Component: openstack-tripleo
Version: trunk
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: Kilo
Assignee: James Slagle
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-31 12:38 UTC by Udi Kalifon
Modified: 2016-05-19 15:44 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-19 15:44:03 UTC
Embargoed:


Attachments (Terms of Use)

Description Udi Kalifon 2015-05-31 12:38:56 UTC
Description of problem:
usage: heat resource-show <NAME or ID> <RESOURCE>

From the above usage message, you'd expect that "heat resource-show" takes the following 2 parameters: 
1) The name or id of the stack (which is "overcloud" in the case of TripleO)
2) The resource's uuid

However, that is only true for top-level resources. In nested resources you have to provide the parent resource's uuid (don't need the stack's name at all) and the resource's name. UUIDs don't work even if it's not a nested resource.


Version-Release number of selected component (if applicable):
heat 0.5.0
python-heatclient-0.5.0-1.el7ost.noarch
openstack-heat-api-2015.1.1-dev11.el7.centos.noarch


How reproducible:
100%


Steps to Reproduce:
1. Deploy an overcloud with TripleO
2. List nested resources with "heat resource-list --nested-depth 5 overcloud"
3. Try to use "heat resource-show" on some top-level resources and some nested ones.

Comment 3 Chandan Kumar 2016-05-19 15:44:03 UTC
This bug is against a Version which has reached End of Life.
If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.


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