Bug 1328202

Summary: support specifying host id as part of /systems api (and hammer content-host commands)
Product: Red Hat Satellite Reporter: Justin Sherrill <jsherril>
Component: APIAssignee: Justin Sherrill <jsherril>
Status: CLOSED ERRATA QA Contact: Tomas Strachota <tstrachota>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bbuckingham, sthirugn, tstrachota
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/14690
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 11:02:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Justin Sherrill 2016-04-18 17:15:35 UTC
For hammer commands it would be very useful to support specifying the host id as part of the 'hammer content-host update' command in addition to uuid.

We could easily support this via the controller

Comment 1 Justin Sherrill 2016-04-18 17:15:37 UTC
Created from redmine issue http://projects.theforeman.org/issues/14690

Comment 2 Justin Sherrill 2016-04-18 17:15:39 UTC
Upstream bug assigned to jsherril

Comment 4 Bryan Kearney 2016-04-20 14:03:07 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/14690 has been closed
-------------
Justin Sherrill
Applied in changeset commit:katello|ff376695d537b00878d1e0b43bb32c465baaff9e.

Comment 5 Tomas Strachota 2016-06-01 13:08:24 UTC
Verified with satellite 6.2 snap 13

$ hammer content-host info --id a95f87f6-a808-4f8e-b965-6a6524fd26fc
Name:                    sat62-client.example.com
ID:                      a95f87f6-a808-4f8e-b965-6a6524fd26fc

$ hammer content-host info --id 2
Name:                    sat62-client.example.com
ID:                      a95f87f6-a808-4f8e-b965-6a6524fd26fc

Comment 6 Bryan Kearney 2016-07-27 11:02:40 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-2016:1501