Bug 1955691 - Applying errata from "Installable Errata" page fails to send the errata to the remote execution page
Summary: Applying errata from "Installable Errata" page fails to send the errata to th...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Errata Management
Version: 6.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Tasos Papaioannou
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-30 16:46 UTC by Ian Ballou
Modified: 2021-05-03 14:18 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)
Fails to pass list. Error "can't be blank" (39.62 KB, image/png)
2021-04-30 16:46 UTC, Ian Ballou
no flags Details
Showing selection of all 225 errata (109.66 KB, image/png)
2021-04-30 16:47 UTC, Ian Ballou
no flags Details

Description Ian Ballou 2021-04-30 16:46:23 UTC
Created attachment 1777853 [details]
Fails to pass list. Error "can't be blank"

Description of problem:

In Satellite 6.7.0 GA, when selecting all (i.e. greater than fits on my screen) and selecting Apply Selected, the page fails to send the list of errata to the job invocation. See attached screenshots.
When an individual erratum is selected, behaviour is normal.
When only the errata displayed on the page are selected (just ticking the all box at the top of the table), behaviour is normal.
When "selecting all 225" (e.g.) and selecting Apply Selected, list is not passed.

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

6.7.0 GA

I've copied this issue from this and following comments on an unrelated BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1405528#c33

I'll let the original author add more details if necessary.

Comment 1 Ian Ballou 2021-04-30 16:47:02 UTC
Created attachment 1777854 [details]
Showing selection of all 225 errata


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