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.
Description of problem:
There is no way to identify the overridden Ansible variables while creating or editing an existing host. Satellite also does not provide the option to override the overridden variables like it does with puppet. If any puppet class is overridden with a value, then it is visible under "Puppet class parameters" and also provides an option to override the value while creating a new host. This option seems to be absent with the Ansible variables.
Version-Release number of selected component (if applicable): 6.6 beta
How reproducible: Always
Steps to Reproduce:
1. Override a Ansible variable for a Ansible role.
2. Then try creating a new host and associate the Ansible role with the host and you will never know that some of the variables are overridden unless you go to the Ansible variables page.
Satellite 6.9 documentation states Ansible variables can be overridden at the Host and Host Group level, but my experience is this is not true. Specifically, the documentation says:
"To use the Ansible variable, add the variable as a parameter to your host or host group, or add the variable as a global parameter." [1]
I was surprised to find I can't set Ansible variables at the Host or Host Group level. Also, maybe related, Ansible variables are not included when Ansible uses Satellite as an inventory source (redhat.satellite.foreman and theforeman.foreman.foreman inventory plugins). Puppet class variables are included with a host's inventory, but not Ansible variables.
Regards
Matthew LeSieur
[1] https://access.redhat.com/documentation/en-us/red_hat_satellite/6.9/html/configuring_satellite_to_use_ansible/getting-started-with-ansible_ansible#overriding-Ansible-variables_ansible
Correction to my previous comment (comment #10). Puppet class variables are not included with a host's inventory when queried using redhat.satellite.foreman or theforeman.foreman.foreman inventory plugins.
Regards
Matthew LeSieur
We are working on displaying the Ansible roles and variables assigned to the host as part of the new host detail page. Users will be also able to override the values from there directly, without going the the complex host edit form. The similar experience for host groups may come later.
Verified on:
Sat 6.11 - 18
Steps to Verify:
1) Create a host.
2) Assign the host an ansible role that includes an overridden variable
3) Navigate to the Host Details page
Actual Results:
Under the Ansible tab, and then the Variables tab, you can see the overridden variable and what it's been set to. You can also change this in the same tab,
either changing the override value, or remove the override.
Expected Results:
Overridden variables are visible as part of the Host Details page.
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 (Moderate: Satellite 6.11 Release), 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-2022:5498