After applying workload tolerations to the hco - it was applied to virt-handler pods, but was not applied to virt-launcher pods. As result - no any VMs can run on tainted nodes

1. tolerations in Kubevirt CR:

$ oc get kubevirt -n openshift-cnv -o json | jq .items[0].spec.workloads
{
"nodePlacement": {
"tolerations": [

{ "effect": "NoSchedule", "key": "key1", "operator": "Equal", "value": "value1" }

]
}
}

1. virt-handler pod has same tolerations and can succesfully run on specified nodes

$ oc get pod -n openshift-cnv virt-handler-zlm4f -o json | jq .spec.tolerations
[
.

{ "effect": "NoSchedule", "key": "key1", "operator": "Equal", "value": "value1" }

,

1. virt-launcher pods does not have same tolerations so can't run on that nodes:

$ oc describe pod
.
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedScheduling 10s default-scheduler 0/3 nodes are available: 3 node(s) had untolerated taint

{key1: value1}

. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling.