Bug 1427554

Summary:	changes in hammer host list output since upgrade from 6.1 to 6.2
Product:	Red Hat Satellite	Reporter:	Manikandan Somasundaram <msomasun>
Component:	Hosts	Assignee:	Daniel Lobato Garcia <dlobatog>
Status:	CLOSED ERRATA	QA Contact:	Peter Ondrejka <pondrejk>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.2.7	CC:	bbuckingham, bkearney, dhlavacd, dlobatog, inecas, jcallaha, kcleveng, mhulan, mmccune, oshtaier, tomckay, tstrachota
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
URL:	http://projects.theforeman.org/issues/18739
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-21 16:45:37 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:

Comment 2 Daniel Lobato Garcia 2017-03-01 09:57:34 UTC

This is happening on upstream too. I'm checking the reason and will submit a fix.

Comment 3 Daniel Lobato Garcia 2017-03-01 10:23:51 UTC

Created redmine issue http://projects.theforeman.org/issues/18739 from this bug

Comment 4 Daniel Lobato Garcia 2017-03-01 10:31:57 UTC

Patch submitted upstream https://github.com/theforeman/hammer-cli-foreman/pull/287

Comment 5 Satellite Program 2017-03-01 13:06:20 UTC

Upstream bug assigned to dlobatog

Comment 6 Satellite Program 2017-03-01 13:06:24 UTC

Upstream bug assigned to dlobatog

Comment 8 Satellite Program 2017-03-06 15:06:20 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/18739 has been resolved.

Comment 10 Peter Ondrejka 2017-08-23 12:04:59 UTC

Verified on Sat 6.3 snap 12, nested hostgroups are now displayed correctly in the output of hammer host list

Comment 12 Bryan Kearney 2018-02-21 16:41:50 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/RHSA-2018:0336

Comment 13 Bryan Kearney 2018-02-21 16:45:37 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/RHSA-2018:0336