Bug 1332626

Summary: REX variable input type doesn't actually see all variables
Product: Red Hat Satellite Reporter: Maxim Burgerhout <mburgerh>
Component: Docs Host Configuration GuideAssignee: Peter Ondrejka <pondrejk>
Status: CLOSED CURRENTRELEASE QA Contact: Russell Dickenson <rdickens>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2.0CC: adahms, mburgerh
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-10 01:27:54 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 Maxim 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.

Comment 5 Andrew Dahms 2016-05-10 01:27:54 UTC
This content is now live on the Customer Portal.

Closing.