Bug 1427554 - changes in hammer host list output since upgrade from 6.1 to 6.2
Summary: changes in hammer host list output since upgrade from 6.1 to 6.2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts
Version: 6.2.7
Hardware: x86_64
OS: Linux
high
high
Target Milestone: Unspecified
Assignee: Daniel Lobato Garcia
QA Contact: Peter Ondrejka
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-28 15:18 UTC by Manikandan Somasundaram
Modified: 2020-06-11 13:21 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:45:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 18739 0 'High' 'Closed' 'Hammer host list output should display hostgroup_title' 2019-12-02 06:33:35 UTC

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
Note You need to log in before you can comment on or make changes to this bug.