Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2108693 - Trying to install all errata causes remote execution to fail
Summary: Trying to install all errata causes remote execution to fail
Keywords:
Status: CLOSED DUPLICATE of bug 2115767
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Errata Management
Version: 6.11.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: 6.13.0
Assignee: Jeremy Lenz
QA Contact: addubey
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-19 17:32 UTC by Jessica Richards
Modified: 2024-03-06 13:03 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-02-08 22:43:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-14000 0 None None None 2023-01-13 17:40:40 UTC

Description Jessica Richards 2022-07-19 17:32:11 UTC
Description of problem:

When the customer tries to remotely install errata on their hosts through the web interface, they're given the option to select all errata, including those that appear beyond the first page of errata.  If they click on that option and then click on the "Install Selected" button, the job fails.  If they click on the "via remote execution - customize first" option, they find that the errata field is empty.  This doesn't happen if they select all of the errata on the first page of errata, but no others.


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

Satellite 6.11


How reproducible:

100%


Steps to Reproduce:
1.  click on the Hosts menu
2.  click on "Content Hosts"
3.  click on the check-mark boxes of one or more hosts
4.  click on the drop-down menu next to the "Select Action" button in the upper-right corner of the page
5.  select "Manage Errata"
6.  click on the check-mark box in the header row of the table in the window that appears, which will enable all of the check-mark boxes in the table
7.  You will see a new message just above the table header that looks like "20 items on this page are selected.  Select all 26."  Click on the link "Select all 26."
8.  click on the drop-down menu next to the "Install Selected" button
9.  select "via remote execution - customize first"

Actual results:

The errata field will be blank.


Expected results:

The errata field should show all of the errata the customer has selected.


Additional info:

- This issue doesn't arise if there are no more than 20 available errata, even if you click the link "Select all 20".
- This issue doesn't arise if you change the number of items the page can display to a number greater than the total number of errata, and then select all errata.

Comment 8 Ian Ballou 2023-02-08 22:43:16 UTC
I'm closing this issue as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2115767 which is already fixed. While one BZ mentions applying errata via the old content host page and the other applies errata via the "Manage Errata" workflow, both use the same underlying bulk select code.

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

Comment 9 Red Hat Bugzilla 2023-09-20 04:25:07 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


Note You need to log in before you can comment on or make changes to this bug.