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:
User with "Ansible Tower Inventory Reader" , can view only Global Parameters but not Host parameters of Hosts
How reproducible:
100%
Steps to Reproduce:
1) Create a satellite user (user1) and assign role "Ansible Tower Inventory Reader" to it.
2) Create hosts parameters for a host :
host_param_test1 : VALUE1
host_param_test2 : VALUE2
3) Run API call to get all parameters:
# curl -X GET -s -k -u [user1]:PASSWORD https://[SATELLITE FQDN]/api/v2/hosts/[Host ID] | jq -r '.all_parameters[].name'
Actual results:
Only the Global parameters are shown.
host_registration_remote_execution
host_registration_insights
host_packages
enable-puppet5
enable-epel
ansible_roles_check_mode
Expected results:
All parameters including Host Parameters.
host_param_test1
host_param_test2
kt_activation_keys
host_registration_remote_execution
host_registration_insights
host_packages
enable-puppet5
enable-epel
ansible_roles_check_mode
Additional info:
1) It affects all current supported satellite versions.
2) After adding "Viewer" role to the user , Host parameters can be retrieved.
3) Ansible tower users , can not import the Host parameters for satellite inventory hosts by following our official documentation for creating non-admin users.
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.10/html/configuring_satellite_to_use_ansible/integrating-ansible-tower_ansible#adding-server-as-a-dynamic-inventory-item_ansible
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you.
Based upon feedback during auto-closure, leaving this bugzilla open a while longer for additional discussion; however, it may be closed in a future iteration.
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.