Description of problem: Version-Release number of selected component (if applicable):CNV 2.4.0 How reproducible:100% Steps to Reproduce: 1. Install CNV 2.4 operator 2. 3. Actual results: virt-handler pod showing Init:CrashLoopBackOff and kubevirt-node-labeller pods are in pending state. Expected results:All pods should be in up and running state. Additional info: output of oc get pods -nopenshift-cnv : kubevirt-node-labeller-7nd2n 0/1 Pending 0 5h16m kubevirt-node-labeller-d6rpf 0/1 Pending 0 5h16m kubevirt-node-labeller-gbmqv 0/1 Pending 0 5h16m virt-handler-2pr74 0/1 Init:CrashLoopBackOff 66 5h16m virt-handler-cwh2m 0/1 Init:CrashLoopBackOff 66 5h16m virt-handler-l98ww 0/1 Init:CrashLoopBackOff 66 5h16m
This is also a side effect of https://github.com/kubevirt/kubevirt/pull/3133 that moved node-labeller and cpu plugin from ssp operator into kubevirt one.
Satyajit can you please post logs from virt-handler?
I have managed to deploy CNV 2.4 (latest) and found that after installation all pods are in running state. Verifying this BZ.
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. https://access.redhat.com/errata/RHSA-2020:3194