Bug 1888588

Summary: [v2v][VMware to CNV VM import API] vmimport.v2v.kubevirt pod remains after imported VM is removed.
Product: Container Native Virtualization (CNV) Reporter: Ilanit Stein <istein>
Component: V2VAssignee: Sam Lucidi <slucidi>
Status: CLOSED ERRATA QA Contact: Ilanit Stein <istein>
Severity: high Docs Contact:
Priority: medium    
Version: 2.5.0CC: cnv-qe-bugs, dagur, fdupont
Target Milestone: ---   
Target Release: 2.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-17 13:24:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
v2v pod screenshot none

Description Ilanit Stein 2020-10-15 09:34:36 UTC
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)

Comment 1 Ilanit Stein 2020-10-19 13:41:24 UTC
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.

Comment 3 Ilanit Stein 2020-10-26 09:01:28 UTC
Verified on CNV-2.5: iib-22696 hco-v2.5.0-396

Now vmimport.v2v.kubevirt pod is removed when the VM import ends.

Comment 6 errata-xmlrpc 2020-11-17 13:24:56 UTC
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