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.
https://github.com/kubevirt/vm-import-operator/pull/416
verified on CNV version: 2.5.0-234
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