Bug 2115767

Summary: Unable to apply all Errata via Remote Execution on Web UI with "Select All"
Product: Red Hat Satellite Reporter: Yogendra <yyadav>
Component: Errata ManagementAssignee: Ian Ballou <iballou>
Status: CLOSED ERRATA QA Contact: addubey
Severity: high Docs Contact:
Priority: high    
Version: 6.11.0CC: ahumbe, damoore, jrichards2, kkinge, pcreech, sadas, saydas
Target Milestone: 6.12.0Keywords: PrioBumpGSS, Regression, Triaged, UserExperience
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-katello-4.5.0.12-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-16 13:35:13 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 Yogendra 2022-08-05 09:58:15 UTC
Description of problem:

When trying to apply all errata using Errata installation via remote execution, the errata filed getting blank on job invocation page.
 
Version-Release number of selected component (if applicable):

Red Hat Satellite 6.11.0

How reproducible:

Steps to Reproduce:
1.Navigate to Hosts -> Content Hosts  
2.Click host on which errata need to be applied
3.Click on Errata installation
4.Now we will get count of 20 errata per-page. Select all errata in one go using "All # items on this page are selected. Select all #"
5.Apply errata via remote execution

Actual results:

Now we will faced the actual issue the job invocation page shows the errata field as blank. So basically no errata can be applied.
 

Expected results:

Should be able to use select all to select all errata and apply them successfully via remote execution

Additional info:

If we increase the count of Entry per page from 20 to something higher so that we can see all errata in one page, then errata application via remote execution is working while using "select all".
 
It seems the same issue was fixed in  bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1846670 but Customer is again hitting this issue on 6.11.

Customer confirm that it was working till 6.10.

Comment 1 Ian Ballou 2022-09-02 20:58:11 UTC
Created redmine issue https://projects.theforeman.org/issues/35484 from this bug

Comment 2 Bryan Kearney 2022-09-03 00:04:38 UTC
Upstream bug assigned to iballou

Comment 3 Bryan Kearney 2022-09-03 00:04:40 UTC
Upstream bug assigned to iballou

Comment 4 Bryan Kearney 2022-09-14 20:04:32 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35484 has been resolved.

Comment 10 errata-xmlrpc 2022-11-16 13:35:13 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.12 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-2022:8506

Comment 11 Ian Ballou 2023-02-08 22:43:16 UTC
*** Bug 2108693 has been marked as a duplicate of this bug. ***

Comment 12 Adam Ruzicka 2023-10-04 11:37:00 UTC
*** Bug 2165198 has been marked as a duplicate of this bug. ***