Bug 1777571

Summary: Hammer command should have option to list hosts in child hostgroups along with parent hostgroup.
Product: Red Hat Satellite Reporter: Karan Kohli <kkohli>
Component: HammerAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: vijsingh
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4.0CC: apatel, kgaikwad, mbacovsk, mshira, ofedoren, rabajaj
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-29 17:13:26 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:

Description Karan Kohli 2019-11-27 20:58:22 UTC 
Description of problem: Should be able to list content hosts under child hostgroup along with parent hostgroup using hammer command.


Version-Release number of selected component (if applicable):
6.4


How reproducible:
100%

Steps to Reproduce:
  1. Create a parent and child hostgroup.
  2. Associate one content host with parent hostgroup and another with child hostgroup.
  3. # hammer host list --hostgroup=Parent_hostgroup  
 ** The above command will list content hosts as per one hostgroup at a time.
 ** There should be option such as "--list_children" or any other so that hosts under child hostgroup are also listed in output.

Actual results:

Not able to list content hosts under child hostgroup along with parent host group using hammer command.

Expected results:

Should be able to list content hosts under child hostgroup along with parent host group using hammer command.
Comment 4 Oleh Fedorenko 2019-11-29 17:13:26 UTC 
This is a problem related to how we send the data from the server through API. For more information please see the related bugzilla.

Closing this as a duplicate. If you think that this is not the same (related) issue, then please reopen.

*** This bug has been marked as a duplicate of bug 1733241 ***