Bug 2269712

Summary: Satellite 6.13/6.14 Remote Execution "Rerun" and "Rerun Failed" button not present with correct Roles applied
Product: Red Hat Satellite Reporter: Benjamin Kielhold <bkielhol>
Component: Remote ExecutionAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.13.0CC: aruzicka
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-03-15 16:06:35 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:

Description Benjamin Kielhold 2024-03-15 15:27:03 UTC
Description of problem:
-----------------------
Creating a user with the correct Role requirements for Remote Execution ("Remote Execution Manager" | "Remote Execution User") does not allow for the user to see the "Rerun" or "Rerun failed" buttons via the Satellite UI at URL: https://{$SATFQDN}/job_invocations/{$job_id} after a job was executed.


Version-Release number of selected component (if applicable):
-------------------------------------------------------------
Tested and verified on
Satellite version 6.13
Satellite version 6.14


How reproducible:
-----------------
100%


Steps to Reproduce:
-------------------
1. Create a User in the Red Hat Satellite.
2. Add the Roles, "Remote Execution Manager" and/or "Remote Execution User" to the newly created User from Step 1.
3. Enter all required fields per user creation and click Submit.
4. Impersonate that user as an Admin or logout and login as the newly created user.
5. Navigate to ~~ Monitor -> Jobs -> Click on a job that previously failed  
6. Only buttons are "Cancel Job" and "Abort Job"

Actual results:
---------------
User is unable to see the "Rerun" or "Rerun failed" buttons and therefore, unable to rerun the same job or rerun a failed job.


Expected results:
-----------------
Attaching the required Roles allow for the user the ability to see the `Rerun` and `Rerun failed` buttons for execution.


Additional info:
----------------
Workaround: To rerun a failed job, the user with the correct permissions per the documentation can append, `/rerun?failed_only=1` to the end of the URL and this will navigate the user to the `Run job` page.

Example URL: 
https://{$SATFQDN}/job_invocations/{$job_id}/rerun?failed_only=1
----------------

Tested on Satellite 6.12.z, the remote execution roles work as expected when adding required Remote Execution Roles to the created user. That user is able to view the `Rerun` and `Rerun failed` buttons when navigating to ~~ Satellite UI -> Monitor -> Jobs -> Clicking a recently executed job. 

Issue is only present on Satellite 6.13 and 6.14.

Reference(s):
Satellite 6.13:
12.3. Permissions for Remote Execution
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html/managing_hosts/configuring_and_setting_up_remote_jobs_managing-hosts#permissions-for-remote-execution_managing-hosts

Satellite 6.14:
12.3. Permissions for Remote Execution
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.14/html/managing_hosts/configuring_and_setting_up_remote_jobs_managing-hosts#permissions-for-remote-execution_managing-hosts

Comment 1 Adam Ruzicka 2024-03-15 15:33:03 UTC
What z-version of 6.13 and 6.14 are you seeing this on?

Comment 2 Benjamin Kielhold 2024-03-15 15:41:35 UTC
Versions listed below that I tested on:
---------------------------------------
Satellite 6.13.6
Satellite 6.14.2

Comment 5 Adam Ruzicka 2024-03-15 16:06:35 UTC
Although it may not seem like it at first glance, this should be a duplicate of BZ2255026, or at least the fix for it should fix this one as well. If I missed any detail that actually makes the two BZs distinct, feel free to reopen.

[1] - https://bugzilla.redhat.com/show_bug.cgi?id=2255026

*** This bug has been marked as a duplicate of bug 2255026 ***