Bug 2220965

Summary: Can no longer select other options in job category other than "Command" for a normal user while scheduling Remote Jobs
Product: Red Hat Satellite Reporter: Puja Singh <pujsingh>
Component: Remote ExecutionAssignee: Adam Ruzicka <aruzicka>
Status: VERIFIED --- QA Contact: Lukáš Hellebrandt <lhellebr>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.13.1CC: ahumbe, aruzicka, lhellebr, onerleka, pcreech, rlavi, zhunting
Target Milestone: 6.14.0Keywords: Regression, Triaged, UserExperience
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rubygem-foreman_remote_execution-10.0.4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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 Puja Singh 2023-07-06 17:59:56 UTC 
Description of problem: 

Not able to select other options in job category other than "Command" for a normal user while scheduling Remote Jobs

Version-Release number of selected component (if applicable): NA


How reproducible:


Steps to Reproduce:

1). Create normal user and add roles except "Administrator" to schedule a remote job. 

2). Login with that user.

3). In Satellite UI --> Go to Hosts --> All Hosts -- > Select a host --> Go to "Schedule a job" and in Job category only "Commands" option is available.

Actual results: Job category should show other options like playbook.


Expected results: 


Additional info: Legacy UI is working fine.
Comment 1 Adam Ruzicka 2023-07-19 15:37:12 UTC 
10.0.4 is out
Comment 2 Lukáš Hellebrandt 2023-07-25 13:23:45 UTC 
Verified with Sat 6.14.0 snap 8.0.

Used reproducer from OP and I was able to schedule the job "Check Update - Script Default" in "Packages" category. The job ran successfully.
Comment 3 Adam Ruzicka 2023-08-09 13:14:45 UTC 
*** Bug 2230442 has been marked as a duplicate of this bug. ***