Bug 2169858

Summary: [Bug] - Unable to fix inhibitors from Satellite WebUI after running preugrade check with leapp.
Product: Red Hat Satellite Reporter: Dhaval Joshi <dhjoshi>
Component: Remote ExecutionAssignee: Maria <magaphon>
Status: CLOSED ERRATA QA Contact: Peter Ondrejka <pondrejk>
Severity: high Docs Contact:
Priority: high    
Version: 6.13.0CC: aruzicka, pcreech, visawant
Target Milestone: 6.13.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: foreman_remote_execution-8.2.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-03 13:25:08 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:
Attachments:
Description Flags
Screenshot none

Description Dhaval Joshi 2023-02-14 20:05:47 UTC 
Created attachment 1944171 [details]
Screenshot

Created attachment 1944171 [details]
Screenshot

Description of problem:
Unable to fix inhibitors from the Satellite WebUI after running preupgrade checks with leapp from WebUI itself.

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

How reproducible:
100%

Steps to Reproduce:
1. Register RHEL 7.9 with the Satellite server, copy ssh keys.
2. Go to Hosts >> All Hosts >> Select the Hosts from List >> Preupgrade Check with leapp
3. Go to Preupgrade report on WebUI >> Select Inhibitor `Missing required answers in the answer file` >> Click Fix Selected
4. Under advanced Fields, it is mandatory to put `remediation_ids`.

Actual results:
 - The remediation id is not mentioned anywhere in the report but since `remediation_ids` field is mandatory, we cannot proceed further.

Expected results:
 - Should be able to run fix inhibitors job without any issues.

Additional info:
In Satellite 6.12, there was no such field for `remediation_ids`. Upon selecting `Fix Selected` option, a remote job has been executed without requesting for `remediation_ids` and inhibitors gets fixed.
Comment 1 Brad Buckingham 2023-02-16 15:27:05 UTC 
Regression based upon statement of new field.  That may be removed once additional details on the field are available.
Comment 3 Adam Ruzicka 2023-02-17 15:23:07 UTC 
Is there a reproducer box? I don't have leapp set up on my satellites
Comment 7 Peter Ondrejka 2023-03-02 09:57:08 UTC 
Verified on Satellite 6.13 snap 12, the remediation job triggered from the leapp preupgrade report tab is now correctly populated with the remediation id (screenshot will follow). The job can be triggered and executes successfully.

For comment 6, most likely the metadata from https://access.redhat.com/articles/3664871 were missing
Comment 11 errata-xmlrpc 2023-05-03 13:25:08 UTC 
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.13 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-2023:2097