Created attachment 1829501 [details] vm Created attachment 1829501 [details] vm Description of problem: After a Plan is successfully completed the VM printableStatus: remains in Provisioning Version-Release number of selected component (if applicable): How reproducible: 100% RHV and vmware Steps to Reproduce: 1. Run A cold migration of source RHV or VMWare VM that is TURNED OFF 2. 3. Actual results: printableStatus: remains in Provisioning Expected results: The VM should be Ready Additional info: 1. Turning the VM on and off corrects this 2. This a regression in 2.2 (2.1 (with vmio) against the same CNV builds doesn't have this issue)
Kubevirt determines the printable status here: https://github.com/kubevirt/kubevirt/blob/e56d0a18679033ab7d42aa903f3286b613dbf216/pkg/virt-controller/watch/vm.go#L16772. In this case it's using the status of the DataVolumes and PVCs to set the Provisioning status. It looks like it shouldn't have the Provisioning status when the DVs have both been successfully imported, but worth asking what the Kubevirt team intended.
Correct link is https://github.com/kubevirt/kubevirt/blob/e56d0a18679033ab7d42aa903f3286b613dbf216/pkg/virt-controller/watch/vm.go#L1677.
It appears that Kubevirt does not notice when the DataVolumes have completed transferring, so the printableStatus of the VM remains at "provisioning" until the VM is reconciled again. Moving to CNV.
Re-assignign this BZ to the storage component as it appears to be about handling the VM's status as related to DVs/PVCs. Please feel free to re-assign if you think this was in error.
It looks like the provisioning finished successfully, but kubevirt doesn't update the printable status for some reason. The next step is to reproduce it and run: oc adm inspect ns/openshift-cnv We should look at the kubevirt controller logs
Created attachment 1839609 [details] inspect
(In reply to Natalie Gavrielov from comment #11) > It looks like the provisioning finished successfully, but kubevirt doesn't > update the printable status for some reason. > The next step is to reproduce it and run: > oc adm inspect ns/openshift-cnv > We should look at the kubevirt controller logs attached (wasn't sure which logs is needed, attached everything)
Michael, Could you please take a look ?
Peter, this breaks VM import so I think we should approve it as a blocker.
Verified on OCP-4.10.0-fc.2 /CNV-4.10.0-674 When MTV a RHEL8 VM cold migration ended successfully the final status seen in OCP web UI Virtualization page for the imported VM is "Stopped", as expected.
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.10.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:0947