Created attachment 1860051 [details] The event error message Description of problem: There is an event if a VM is not live migratable for some reason. However, in the API conditions there is a reason (a really nice one!) of why the VM is not livemigrateable. This reason should be included in the event as well. Version-Release number of selected component (if applicable): 4.10 How reproducible: Always Steps to Reproduce: 1. Create a VM which is not live migratable i.e. using local storage (as in the screenshot) 2. 3. Actual results: Expected results: Additional info:
Created attachment 1860053 [details] The (better) API error message
Checked with: iib:219905 [cnv-qe-jenkins@virt-akr-411-jpqfs-executor ~]$ oc get vmi NAME AGE PHASE IP NODENAME READY rhel9-fatal-camel 7m12s Running 10.128.2.14 virt-akr-411-jpqfs-worker-0-j99b5 True [cnv-qe-jenkins@virt-akr-411-jpqfs-executor ~]$ oc describe vm rhel9-fatal-camel | grep Message Message: cannot migrate VMI: PVC rhel9-fatal-camel-rootdisk-ekzpj is not shared, live migration requires that all PVCs must be shared (using ReadWriteMany access mode) Type Reason Age From Message [cnv-qe-jenkins@virt-akr-411-jpqfs-executor ~]$ oc get vm rhel9-fatal-camel -o json | jq '.spec.dataVolumeTemplates' | grep storageClassName "storageClassName": "hostpath-csi-basic",
PR is in merge pool
Backport PR is not merged yet. Moving back to POST.
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