Bug 2214285
| Summary: | User with only view-host permission can attempt to schedule a job which leads to Categories list failed with: Request failed with status code 403 | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | addubey |
| Component: | Remote Execution | Assignee: | Maria <magaphon> |
| Status: | CLOSED ERRATA | QA Contact: | Pavel Novotny <pnovotny> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.14.0 | CC: | aruzicka, pcreech, rlavi |
| Target Milestone: | 6.15.0 | Keywords: | Triaged, UserExperience |
| Target Release: | Unused | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | foreman_remote_execution-11.1.0 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-04-23 17:11:22 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Is this a regression from earlier Satellite release? Is there a stack trace that can be attached? This is in progress Bulk setting Target Milestone = 6.15.0 where sat-6.15.0+ is set. I forked off the secondary issue into its own BZ[1]. A fix for this BZ as described in #0 is now fixed and released in upstream. [1] - https://bugzilla.redhat.com/show_bug.cgi?id=2247498 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: