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.
DescriptionMaxim Burgerhout
2016-05-03 15:16:25 UTC
Document URL:
https://access.redhat.com/documentation/en/red-hat-satellite/6.2-beta/host-configuration-guide/chapter-12-running-remote-jobs-on-satellite-hosts
Section Number and Name:
CHAPTER 12. RUNNING REMOTE JOBS ON SATELLITE HOSTS
Describe the issue:
Not all variables that are in the YAML ENC output are usable for the variable input type in REX. Only variables that are visible on the parameters tab of a system are usable.
For example: kt_activiation_keys is on the parameters tab and is thus usable in REX directly. Other variables that are in the YAML output, like kt_cv and environment, are not available in REX for the variable input type, but you can use them as @host.kt_cv in the script itself.
Suggestions for improvement:
It would make sense to at least document the above. It seems a little odd that variables I can see in the YAML output are sometimes no visible to REX (if they are parameters like 'puppetmaster', implicitly inherited from a host group) and sometimes are visible: if I set 'puppetmaster' as a global parameter, it will be visible to REX, even though it shows up in the ENC YAML output exactly the same.
Additional information:
It might be enough to point out that global variables need to be visible on the host's parameters tab, or even have a [?] to explain this while configuring a template input field with variable type.