Description of problem: Cant start VM backed by a PVC that is owned by a DataVolume Version-Release number of selected component (if applicable): CNV 4.8.0 How reproducible: 100% Steps to Reproduce: 1. Start a VM backed by the underlying PVC of a DataVolume Actual results: VM 'Scheduled' Expected results: VM 'Running' Additional info: Manifests and additional info in comment #1.
Re-assigning component to Storage as this appears to be more related to that component. If you think this is incorrect, please feel free to re-assign to Virtualization again.
Bartosz, could you please take a look for the bug?
@yadu Do you still need more info?
Adam, could you please check Alex's comment?
According to Alexander Wels this is only related to the issue in d/s builds where the qemu user wasn't being created in the virt-launcher pod. This has been fixed so moving this to ON_QA.
(In reply to Adam Litke from comment #11) > According to Alexander Wels this is only related to the issue in d/s builds > where the qemu user wasn't being created in the virt-launcher pod. This has > been fixed so moving this to ON_QA. I see, but, for the direct usage of DVs we wouldn't need the qemu user and wouldn't have tackled this issue, don't we want to dig deeper as to why? I believe this occurs due to the different flow for PVCs that that replaces them with hostDisk and somewhere along the lines needs the qemu user for those ops. (Comment #8) @alitke
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