Bug 1834205 - Node checker intersection is wrong in Affinity Modal
Summary: Node checker intersection is wrong in Affinity Modal
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.5
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.5.0
Assignee: Gilad Lekner
QA Contact: Radim Hrazdil
Depends On:
TreeView+ depends on / blocked
Reported: 2020-05-11 10:19 UTC by Gilad Lekner
Modified: 2020-07-13 17:37 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-07-13 17:37:10 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 5377 0 None closed Bug 1834205: Node checker intersection is wrong in Affinity Modal 2020-08-26 05:39:17 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:37:19 UTC

Description Gilad Lekner 2020-05-11 10:19:45 UTC
Description of problem:
When creating a Node Affinity, the node checker intersects Expressions and Fields even
if one of the arrays is empty, causing an empty qualified nodes array even where there are qualified nodes.

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

How reproducible:

Steps to Reproduce:
1. Create node affinity, add a valid expression
2. Leave fields labels empty

Actual results:
no qualified nodes found

Expected results:
should find qualified nodes

Additional info:

Comment 4 Radim Hrazdil 2020-05-20 09:04:07 UTC
Verified in console release-4.5 branch commit: 5994c64ee529b650bae348ef78ebc23dca8db5c5

Comment 5 errata-xmlrpc 2020-07-13 17:37:10 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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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