This bug was initially created as a copy of Bug #2073669 I am copying this bug because: Description of problem: [kbidarka@localhost ocs]$ oc get vm NAME AGE STATUS READY vm-rhel84-ocs 14m Starting False [kbidarka@localhost ocs]$ oc get vmi oc getNAME AGE PHASE IP NODENAME READY vm-rhel84-ocs 10m Scheduling False [kbidarka@localhost ocs]$ oc get pods NAME READY STATUS RESTARTS AGE virt-launcher-vm-rhel84-ocs-72ftd 0/1 CreateContainerError 0 10m [kbidarka@localhost ocs]$ oc describe pod virt-launcher-vm-rhel84-ocs-72ftd | grep -A 10 "Events" Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 11m default-scheduler Successfully assigned default/virt-launcher-vm-rhel84-ocs-72ftd to c01-kbid-411-bzc6s-worker-0-mttrb Normal SuccessfulAttachVolume 11m attachdetach-controller AttachVolume.Attach succeeded for volume "pvc-48e17311-2aea-42b0-a486-3ebced03269a" Normal SuccessfulMountVolume 11m kubelet MapVolume.MapPodDevice succeeded for volume "pvc-48e17311-2aea-42b0-a486-3ebced03269a" globalMapPath "/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/pvc-48e17311-2aea-42b0-a486-3ebced03269a/dev" Normal SuccessfulMountVolume 11m kubelet MapVolume.MapPodDevice succeeded for volume "pvc-48e17311-2aea-42b0-a486-3ebced03269a" volumeMapPath "/var/lib/kubelet/pods/4fb62855-f55c-4833-825f-26c018c27385/volumeDevices/kubernetes.io~csi" Normal AddedInterface 10m multus Add eth0 [10.128.3.80/23] from openshift-sdn Warning Failed 10m (x2 over 10m) kubelet Error: container create failed: time="2022-04-09T12:42:59Z" level=error msg="runc create failed: unable to start container process: exec: \"/usr/bin/virt-launcher-monitor\": stat /usr/bin/virt-launcher-monitor: no such file or directory" Warning Failed 10m kubelet Error: container create failed: time="2022-04-09T12:43:00Z" level=error msg="runc create failed: unable to start container process: exec: \"/usr/bin/virt-launcher-monitor\": stat /usr/bin/virt-launcher-monitor: no such file or directory" Warning Failed 10m kubelet Error: container create failed: time="2022-04-09T12:43:15Z" level=error msg="runc create failed: unable to start container process: exec: \"/usr/bin/virt-launcher-monitor\": stat /usr/bin/virt-launcher-monitor: no such file or directory" Version-Release number of selected component (if applicable): CNV-4.11 v4.11.0-204 RHEL 8 211736 How reproducible: Smoke Tests Failing. Steps to Reproduce: 1. Create a VM using RHEL-8 CNV Builds 2. Start the VM 3. Actual results: level=error msg="runc create failed: unable to start container process: exec: \"/usr/bin/virt-launcher-monitor\": stat /usr/bin/virt-launcher-monitor: no such file or directory" Expected results: Starting a VM should be successful Additional info:
checked using iib:219905 [cnv-qe-jenkins@virt-akr-411-jpqfs-executor ~]$ oc get vm NAME AGE STATUS READY vm-rhel84-ocs 68m Running True [cnv-qe-jenkins@virt-akr-411-jpqfs-executor ~]$ oc get vmi NAME AGE PHASE IP NODENAME READY vm-rhel84-ocs 65m Running 10.129.2.99 virt-akr-411-jpqfs-worker-0-rt6lf True [cnv-qe-jenkins@virt-akr-411-jpqfs-executor ~]$ oc get dv NAME PHASE PROGRESS RESTARTS AGE dv-rhel84-ocs Succeeded 100.0% 4m
Also smoke tests are Passing now. Will mark this as VERIFIED.
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 (Important: OpenShift Virtualization 4.11.0 Images security and bug fix 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:6526