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.

Description of problem:
Trying to apply all errata on the content host from satellite webui via remote execution fails to pass the errata list to remote execution job and throws error "can't be blank".

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

How reproducible:
always

Steps to Reproduce:
1. Select content host with installable errata and open the errata tab
2. Select all the errata on the page and click on the blue hyperlink "Select all XX"
3. Apply Selected >> Via remote execution

Actual results:
The job invocation page shows error 'Can't be blank' as the errata list is empty

Expected results:
it should start a job to apply all selected errata.

Additional info:
Seems a Regression of BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1838719

This looks like a duplicate of BZ #2115767. If you feel this BZ is different from enough from the other one to warrant being tracked separately, feel free to reopen.

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