Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1313056

Summary:	hammer cli : hostgroup info is not showing content-related fields
Product:	Red Hat Satellite	Reporter:	Brad Buckingham <bbuckingham>
Component:	Hosts - Content	Assignee:	Partha Aji <paji>
Status:	CLOSED ERRATA	QA Contact:	jcallaha
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	bbuckingham, dlezzoum, inecas, jcallaha, paji, pcfe, rnuccite, zhunting
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-hammer_cli_katello-0.11.3.5-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-21 16:54:17 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 Brad Buckingham 2016-02-29 20:08:48 UTC

Description of problem:

Bug 1267629 raised the issue that content-related fields are not included as part of the API.  This included fields such as the following:

    "content_source_id": 1,
    "content_source_name": "katello-centos7-devel",
    "content_view_id": 1,
    "content_view_name": "Default Organization View",
    "lifecycle_environment_id": 1,
    "lifecycle_environment_name": "Library",

That issue has since been addressed; however, the fields should also be visible from the hammer cli.

Version-Release number of selected component (if applicable):
Satellite 6.1 and prior.

How reproducible:
Always

Steps to Reproduce:
1. create a hostgroup that contains a content source, lifecycle environment and content view
2. perform a 'hammer hostgroup info --id [id]'
3.

Actual results:

hammer> hostgroup info --id 1
Id:                     1
Name:                   group1
Title:                  group1
Puppet CA Proxy Id:     1
Puppet Master Proxy Id: 1
Puppetclasses:          

Parameters:             

Organizations:          
    Default Organization
Parent Id:

Expected results:

The output should include details on the content source, lifecycle environment and content view associated with the host group.

Additional info:

Comment 2 Bryan Kearney 2016-07-26 15:25:24 UTC

Moving 6.2 bugs out to sat-backlog.

Comment 3 Bryan Kearney 2016-07-26 15:34:46 UTC

Moving 6.2 bugs out to sat-backlog.

Comment 5 Brad Buckingham 2017-02-10 13:27:17 UTC

The issue raised by this bugzilla has been partially addressed by bug 1360136.  That bug added the content view and lifecycle environment to hammer-cli-katello; however, it did not include content source.  For completeness, we should also extend it to include content source.

Comment 6 Amit Upadhye 2017-02-15 15:19:13 UTC

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

Comment 7 Satellite Program 2017-02-21 15:21:15 UTC

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

Comment 8 Djebran Lezzoum 2017-06-22 06:50:09 UTC

verified and passed automation test on satellite 6.3.0 snap 3

Comment 13 Djebran Lezzoum 2017-07-06 16:36:54 UTC

Think the ids here are mandatory as without them we cannot understand from which organization we got the content view and lifecycle environment

as the --query-organization is used at creation stage and not shown/saved at later stage.

and even if with hammer --output="json" we cannot get that ids

Move to ASSIGNED as for more consistency the fields
      - content_source_id
      - content_view_id
      - lifecycle_environment_id
are also needed.

Comment 15 Partha Aji 2017-12-08 16:15:03 UTC

Connecting redmine issue http://projects.theforeman.org/issues/21912 from this bug

Comment 16 Brad Buckingham 2017-12-15 22:51:45 UTC

Upstream PR merged. Moving to POST.

Comment 20 jcallaha 2018-02-07 19:43:01 UTC

Verified in Satellite 6.3 Snap 35

-bash-4.2# hammer hostgroup info --id 1
Id:                     1
Name:                   rhel74
Title:                  rhel74
Operating System:       RHEL Server 7.4
Subnet:                 Default Subnet
Domain:                 idmqe.lab.eng.bos.redhat.com
Architecture:           x86_64
Partition Table:        Kickstart default
Puppet CA Proxy Id:     
Puppet Master Proxy Id: 
ComputeProfile:         2-Medium
Puppetclasses:          

Parameters:             
    kt_activation_keys => rhel7
Locations:              
    Default Location
Organizations:          
    Default Organization
Parent Id:              
OpenSCAP Proxy:         
Content View:           
    ID:   2
    Name: rhel7
Lifecycle Environment:  
    ID:   1
    Name: Library
Content Source:         
    ID:   1
    Name: yttrium.idmqe.lab.eng.bos.redhat.com
Kickstart Repository:   
    ID:   20
    Name:

Comment 21 Satellite Program 2018-02-21 16:54:17 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