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 1295770

Summary: hammer listing the sc-params doesn't displays the associated puppet class.
Product: Red Hat Satellite Reporter: Jitendra Yejare <jyejare>
Component: HammerAssignee: orabin
Status: CLOSED ERRATA QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: NightlyCC: bkearney, ehelms
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/12998, http://projects.theforeman.org/issues/13101
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 11:16:49 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:
Bug Depends On:    
Bug Blocks: 1278718    
Attachments:
Description Flags
Screenshot Attached.
none
[Verified] Screenshot Attached none

Description Jitendra Yejare 2016-01-05 12:24:17 UTC
Created attachment 1111816 [details]
Screenshot Attached.

Description of problem:
List the smart class parameters using hammer command :
'hammer -u <user> -p <passwd> sc-param list'
or with any subcommands available to display sc-params which has PUPPET_CLASS column.

Version-Release number of selected component (if applicable):
foreman-1.11.0-0.develop.201512111432git98f6ca5.el7.noarch

How reproducible:
Always

Steps to Reproduce:
1. List the smart class parameters in satellite using hammer.
2.
3.

Actual results:
List doesn't shows the associated Puppet Class for each parameter under column 'PUPPET_CLASS'

Expected results:
List should show the associated Puppet Class for each parameter under column 'PUPPET_CLASS'

Additional info:

Comment 3 Bryan Kearney 2016-01-05 13:05:41 UTC
Upstream bug component is Provisioning

Comment 4 Bryan Kearney 2016-01-10 13:05:12 UTC
Upstream bug component is Hammer

Comment 5 Bryan Kearney 2016-02-10 22:12:59 UTC
Upstream bugs are marked as closed. This bug will be included in 6.2

Comment 7 Jitendra Yejare 2016-03-23 06:58:52 UTC
The issue is still reproducible in Sat 6.2 snap 4.

Its not showing associated puppet class name.

Moving the state to 'Failed QA'.

Comment 12 Jitendra Yejare 2016-05-19 12:53:44 UTC
Created attachment 1159470 [details]
[Verified] Screenshot Attached

Comment 13 Jitendra Yejare 2016-05-19 12:53:57 UTC
Verified !

@Sat 6.2 Snap 11

Listing smart class parameters shows the puppet class for each parameter as UI.

Verified Screenshot Attached.

Comment 14 Bryan Kearney 2016-07-27 11:16:49 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/RHBA-2016:1501