Bug 1042645 - resource_types is not supported in the client
Summary: resource_types is not supported in the client
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-heatclient
Version: 4.0
Hardware: All
OS: Linux
high
high
Target Milestone: z1
: 4.0
Assignee: Jakub Ruzicka
QA Contact: Steve Baker
URL:
Whiteboard:
Depends On:
Blocks: 996596
TreeView+ depends on / blocked
 
Reported: 2013-12-13 01:03 UTC by Angus Salkeld
Modified: 2014-02-04 17:20 UTC (History)
8 users (show)

Fixed In Version: python-heatclient-0.2.6-3.el6ost
Doc Type: Bug Fix
Doc Text:
Previously, heatclient support for the resource_types API was missing. With this update, resource_types support has been backported, and the 'resource-type-list' and 'resource-type-show' commands are available in heatclient.
Clone Of:
Environment:
Last Closed: 2014-01-23 14:23:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 61624 0 None None None Never
Red Hat Product Errata RHBA-2014:0046 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform 4 Bug Fix and Enhancement Advisory 2014-01-23 00:51:59 UTC

Description Angus Salkeld 2013-12-13 01:03:19 UTC 
Description of problem:
We have an api for getting the resource_types, but the client support seems to have been overlooked.

https://bugs.launchpad.net/python-heatclient/+bug/1260130
Comment 1 Angus Salkeld 2013-12-13 01:04:16 UTC 
https://review.openstack.org/#/c/61624/
Comment 6 Jakub Ruzicka 2014-01-08 14:22:03 UTC 
To verify this, make sure following commands work:

$ heat resource-type-list
$ heat resource-type-show <resource type>
Comment 7 Jakub Ruzicka 2014-01-09 17:32:17 UTC 
Fix backported.
Comment 11 Steve Baker 2014-01-15 23:53:51 UTC 
Confirmed that this feature now exists and is working as expected on python-heatclient 0.2.6-3.el6ost
Comment 14 Lon Hohberger 2014-02-04 17:20:16 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://rhn.redhat.com/errata/RHBA-2014-0046.html
Note You need to log in before you can comment on or make changes to this bug.