+++ This bug was initially created as a clone of Bug #1985649 +++ Description of problem ---------------------- Creation of VirtualMachines with cloud-init is failing due to virt-handler Pod missing the xorrisofs command: > server error. command SyncVMI failed: "generating local cloud-init data failed: exec: \"xorrisofs\": executable file not found in $PATH" Version ------- $ oc get csv -A NAMESPACE NAME DISPLAY VERSION REPLACES PHASE openshift-cnv kubevirt-hyperconverged-operator.v4.8.2 OpenShift Virtualization 4.8.2 kubevirt-hyperconverged-operator.v4.8.1 Succeeded OCP: 4.8.7 CNV: v4.8.2 KubeVirt: v0.41.3-6-gb05c0479e virt-handler: v4.8.2-1 hco-bundle-registry: v4.9.0-57 (2021-07-24) IIB image: registry-proxy.engineering.redhat.com/rh-osbs/iib:103327 => http://cnv-version-explorer.apps.cnv.engineering.redhat.com/BundleDetails?ver=v4.9.0-57 How reproducible ---------------- 100% Steps to Reproduce ------------------ Create a VirtualMachine with a cloud-init disk. Actual results -------------- The VirtualMachineInstance stays in Scheduled Phase because the virt-handler Pod is failing to generate the cloud-init disk: Normal SuccessfulCreate 79s virtualmachine-controller Created virtual machine pod virt-launcher-container-disk-vm-1630222532-2495804-4sb5x Warning SyncFailed 21s (x14 over 64s) virt-handler server error. command SyncVMI failed: "generating local cloud-init data failed: exec: \"xorrisofs\": executable file not found in $PATH" Expected results ---------------- The VirtualMachine should start properly. --- Additional comment from Igor Bezukh on 2021-08-01 18:25:26 UTC --- Hi, Following is the link to the bugfix: https://code.engineering.redhat.com/gerrit/c/kubevirt/+/259221 I couldn't add it as a link to the bug, there is some invalid Bug ID error that always appears if I propose this link as Red Hat Engineering Gerrit link I've validated that xorriso is already in the container starting from virt-launcher-container-v4.9.0-15 Moving the bug to ON_QA --- Additional comment from Denis Ollier on 2021-08-02 15:48:11 UTC --- Verified with http://cnv-version-explorer.apps.cnv.engineering.redhat.com/BundleDetails?ver=v4.9.0-66.
Submitted midstream patchset: https://code.engineering.redhat.com/gerrit/c/kubevirt/+/268489
[kbidarka@localhost fedora]$ oc get vmi NAME AGE PHASE IP NODENAME vm-fedora 3m4s Running 10.131.1.92 t3-pytest-48-f6tln-worker-0-qcrrg [kbidarka@localhost fedora]$ oc get pods NAME READY STATUS RESTARTS AGE virt-launcher-vm-fedora-sxt7z 2/2 Running 0 3m35s [kbidarka@localhost fedora]$ oc rsh virt-launcher-vm-fedora-sxt7z Defaulting container name to compute. Use 'oc describe pod/virt-launcher-vm-fedora-sxt7z -n openshift-virtualization-os-images' to see all of the containers in this pod. sh-4.4# virsh list Id Name State -------------------------------------------------------------- 1 openshift-virtualization-os-images_vm-fedora running sh-4.4# which xorrisofs /usr/bin/xorrisofs sh-4.4# ls -l /usr/bin/xorrisofs lrwxrwxrwx. 1 root root 7 Jan 7 2019 /usr/bin/xorrisofs -> xorriso sh-4.4# exit exit --- VERIFIED with virt-launcher/images/v4.8.2-2
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.2 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-2021:3598