Created attachment 1845389 [details] node was found after typing key Description of problem: Node selector/tolerations rules are evaluated too early, the node was found even without input value, without value inputed, the VM is not schedulable. The node should only be found after typing key and value. $ oc describe pod virt-launcher-fedora-k7spt Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning FailedScheduling 15s default-scheduler 0/6 nodes are available: 1 node(s) had taint {key: test}, that the pod didn't tol erate, 2 node(s) didn't match Pod's node affinity/selector, 3 node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn't tolerate. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. label a node key=test 2. create a vm and add label in node selector by just adding key. 3. start the vm Actual results: node was found by just typing key there. Expected results: node was only found by typing key=test. Additional info:
verified on master
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 (Moderate: OpenShift Container Platform 4.10.3 security update), 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:0056