Created attachment 1721785 [details] v2v pod screenshot Description of problem: After VM is imported from VMware to CNV via api (vmio), the vmimport.v2v.kubevirt pod remains (with no owner). Version-Release number of selected component (if applicable): OCP-4.6/CNV-2.5(deployed @Oct 11 2020)
Apparently, removing of an imported VM not only leaves the vmimport.v2v.kubevirt pod, but also the PVCs appear in status "Terminating" and the PVs remain with no change. Removing the vmimport.v2v.kubevirt pod removes also the VMs PVCs and PVs Stating this here as it all seem to be related to the same problem. If this is another problem, and another BZ should be filed please update.
https://github.com/kubevirt/vm-import-operator/pull/426
Verified on CNV-2.5: iib-22696 hco-v2.5.0-396 Now vmimport.v2v.kubevirt pod is removed when the VM import ends.
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 (OpenShift Virtualization 2.5.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/RHEA-2020:5127