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.
Document URL:
https://access.redhat.com/documentation/en/red-hat-satellite/6.2/single/puppet-guide
Describe the issue:
The puppet guide does not talk about the usage of Puppet variables and steps to import/add them into the Satellite 6.2. I had couple of cases so far in which the customers were confused between the usage of smart variables and smart class parameters
Additional information: NA
Created attachment 1270525[details]
Using the Smart Variable Tool
Hello Mihir
The attached PDF contains the new, for this bug, section "Using the Smart Variable Tool". It appears after the recently updated section, already published[1], "Configuring Smart Class Parameters from Puppet Classes". I included both section in the PDF for ease of review. Please ask the customer if things are now much clearer and if any further changes are required.
[1] We did that part in Bug 1381781
Thank you