Description of problem ---------------------- virt-handler Pod failing to start due to virt-launcher Init container in CrashLoopBackOff state. Version ------- OCP: v4.8.0-0.nightly-2021-04-09-222447 CNV: v4.8.0 KubeVirt: v0.40.0-rc.0-81-gd2eb0cf hco-bundle-registry: v4.8.0-252 (2021-04-13 15:59:52) IIB image: registry-proxy.engineering.redhat.com/rh-osbs/iib:66169 How reproducible ---------------- 100% Steps to Reproduce ------------------ Install CNV from IIB image registry-proxy.engineering.redhat.com/rh-osbs/iib:66169. Actual results -------------- virt-handler Pod failing to start due to virt-launcher Init container in CrashLoopBackOff state: > virt-handler-987pr 0/1 Init:CrashLoopBackOff 132 10h > virt-handler-hh82v 0/1 Init:CrashLoopBackOff 132 10h > virt-handler-hwmmn 0/1 Init:CrashLoopBackOff 132 10h Expected results ---------------- virt-handler Pod should start properly Additional info --------------- Logs from virt-launcher Pod say it's failing because node-labeller.sh script is missing. > oc -n openshift-cnv logs virt-handler-987pr -c virt-launcher > > /bin/sh: /bin/node-labeller.sh: No such file or directory
@Karel can you look at this BZ?
Verified with: - hco-bundle-registry:v4.8.0-259 - registry-proxy.engineering.redhat.com/rh-osbs/iib:66881 - registry-proxy.engineering.redhat.com/rh-osbs/container-native-virtualization-virt-handler:v4.8.0-41
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 Virtualization 4.8.0 Images), 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-2021:2920