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:
Currently there is not filter or roles in satellite which allows non-admin user set the release version for a content host. When they click on the dropdown, a busy state icon appears and stays forever.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Create a non-admin user on satellite GUI.
2. There is no such roles or feature which allows him to set the release version for content host.
3.
Actual results:
non-admin user can not set release version for a content host and when they click on the drop-down, a busy state icon appears and stays forever.
Expected results:
non-admin user should be allowed to set release version for a content host
Additional info:
This bug has been has already been fixed in upstream.
https://projects.theforeman.org/issues/24395