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 1970428[details]
page_view
Description of problem: User with only view-host permission can attempt to schedule a job which leads to errors -> Categories list failed with Request failed with status code 403
Version-Release number of selected component (if applicable): 6.14.0 snap -3
How reproducible: Always
Steps to Reproduce:
1. Create a user with a view-host permission
2. Navigate to Hosts -> All hosts -> select host
3. Try to click on the schedule job button, it opens up a broken page for initiating the rex job.
Actual results: Page opens up stating Job category - Error and States -> Categories list failed with: Request failed with status code 403
Expected results: I believe users with such permission should not be able to run/click on the schedule job button like the dropdown of all jobs is locked for example.
Additional info:
Verified in Sat 6.15 snap 2:
satellite-6.15.0-1.el8sat.noarch
rubygem-foreman_remote_execution-11.1.1-1.el8sat.noarch
User with 'View hosts' role can no longer schedule a job from the host list or from the host detail, all the buttons for runnig jobs, such as 'Schedule Remote Job', 'Schedule a job', 'Run all Ansible roles' and similar others are not shown in the action menu.
As mentioned in bug 2247498, the user can still access the 'Run job' page via /job_invocations/new URL but it is somewhat broken so no job can be executed.
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 (Important: Satellite 6.15.0 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-2024:2010
Created attachment 1970428 [details] page_view Description of problem: User with only view-host permission can attempt to schedule a job which leads to errors -> Categories list failed with Request failed with status code 403 Version-Release number of selected component (if applicable): 6.14.0 snap -3 How reproducible: Always Steps to Reproduce: 1. Create a user with a view-host permission 2. Navigate to Hosts -> All hosts -> select host 3. Try to click on the schedule job button, it opens up a broken page for initiating the rex job. Actual results: Page opens up stating Job category - Error and States -> Categories list failed with: Request failed with status code 403 Expected results: I believe users with such permission should not be able to run/click on the schedule job button like the dropdown of all jobs is locked for example. Additional info: