Bug 1886694

Summary: [v2v][VMware to CNV VM import API] VM import reconcile loop cause VMware SDK service to become stuck.
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: high    
Version: 2.5.0CC: cnv-qe-bugs, dagur, fdupont, mnadeem
Target Milestone: ---Keywords: AutomationBlocker
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:

Description Ilanit Stein 2020-10-09 06:47:34 UTC
Description of problem:
VM import from VMware to RHV via API (VMIO) retries cause the VMware SDK being not accessible. 
This happened in a case of the NFS target storage became not available, as well as the vddk-init-image. 
 
Fabien Dupont:
The reason is that the provider client for VMware doesn't close its session, so for each iteration of the reconcile loop, it opens a new session that stucks up in VMware SDK service. After some time, no more sessions are available and you have the HTTP 503. Fortunately, Sam has already created a pull request to fix it: https://github.com/kubevirt/vm-import-operator/pull/416. 

You don't have to cancel the import. Once the VMware service is restarted (that clears all sessions), you can delete the vm-import-controller pod and it will resume the import.

Version-Release number of selected component (if applicable):
CNV-2.5, iib:18173

Additional information:
To overcome the VMware SDK access issue, Vcenter VM restart was required.

Comment 5 Md Nadeem 2020-10-23 13:49:47 UTC
verified on CNV version: 2.5.0-234

Comment 8 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