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_view_name": "Default Organization View",
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.
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]'
hammer> hostgroup info --id 1
Puppet CA Proxy Id: 1
Puppet Master Proxy Id: 1
The output should include details on the content source, lifecycle environment and content view associated with the host group.
Moving 6.2 bugs out to sat-backlog.
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.
Created redmine issue http://projects.theforeman.org/issues/18523 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/18523 has been resolved.
verified and passed automation test on satellite 6.3.0 snap 3
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
are also needed.
Connecting redmine issue http://projects.theforeman.org/issues/21912 from this bug
Upstream PR merged. Moving to POST.
Verified in Satellite 6.3 Snap 35
-bash-4.2# hammer hostgroup info --id 1
Operating System: RHEL Server 7.4
Subnet: Default Subnet
Partition Table: Kickstart default
Puppet CA Proxy Id:
Puppet Master Proxy Id:
kt_activation_keys => rhel7
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.