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.
Created attachment 1431272[details]
Screenshot of Administer -> Settings -> Ansible
Description of problem:
Parameters not available to roles directly as variables: setting to enable that is missing
Version-Release number of selected component (if applicable):
satellite-6.4.0-3.beta.el7sat.noarch
rubygem-smart_proxy_ansible-2.0.2-3.el7sat.noarch
tfm-rubygem-foreman_ansible_core-2.0.2-1.el7sat.noarch
tfm-rubygem-foreman_ansible-2.0.4-1.el7sat.noarch
ansible-2.4.2.0-2.el7.noarch
How reproducible:
always
Steps to Reproduce:
1. Have Satellite with some ansible role imported (I have used linuxhq.setup
from Ansible Galaxy)
2. Have a host with that role assigned and add a parameter
"setup_motd: Hello world" to it
3. Hosts -> All hosts -> <host> -> Run Ansible roles
Actual results:
Variable/parameter is not propagated into role.
Expected results:
Variable is accessible to the role.
Additional info:
Looking into inventory file generated by Satellite:
[root@sat640snap1 ~]# cat /tmp/foreman-inventories/24656315-97ca-406c-b841-7e7a7281fc1a | json_reformat
{
"all": {
"hosts": [
"rhel74.example.com"
],
"vars": {
}
},
"_meta": {
"hostvars": {
"rhel74.example.com": {
[...]
"foreman_params": {
"setup_motd": "Hello world",
[...]
}
So looks like variable is there, but not as "setup_motd", but as "foreman_params.setup_motd". This is supposed to be configurable, but it is not. See attached screenshot.
I see "Top level Ansible variables" with snap 10, satellite-6.4.0-10.beta.el7sat.noarch and foreman_ansible 2.2.1
but the settings seems to have no effect, params are always hidden under foreman_params key
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/RHSA-2018:2927
Created attachment 1431272 [details] Screenshot of Administer -> Settings -> Ansible Description of problem: Parameters not available to roles directly as variables: setting to enable that is missing Version-Release number of selected component (if applicable): satellite-6.4.0-3.beta.el7sat.noarch rubygem-smart_proxy_ansible-2.0.2-3.el7sat.noarch tfm-rubygem-foreman_ansible_core-2.0.2-1.el7sat.noarch tfm-rubygem-foreman_ansible-2.0.4-1.el7sat.noarch ansible-2.4.2.0-2.el7.noarch How reproducible: always Steps to Reproduce: 1. Have Satellite with some ansible role imported (I have used linuxhq.setup from Ansible Galaxy) 2. Have a host with that role assigned and add a parameter "setup_motd: Hello world" to it 3. Hosts -> All hosts -> <host> -> Run Ansible roles Actual results: Variable/parameter is not propagated into role. Expected results: Variable is accessible to the role. Additional info: Looking into inventory file generated by Satellite: [root@sat640snap1 ~]# cat /tmp/foreman-inventories/24656315-97ca-406c-b841-7e7a7281fc1a | json_reformat { "all": { "hosts": [ "rhel74.example.com" ], "vars": { } }, "_meta": { "hostvars": { "rhel74.example.com": { [...] "foreman_params": { "setup_motd": "Hello world", [...] } So looks like variable is there, but not as "setup_motd", but as "foreman_params.setup_motd". This is supposed to be configurable, but it is not. See attached screenshot.