Bug 1786355

Description of problem:
Not able to import VM after import of a large disk:

See also related Bug 1786293 - [v2v] Large disk - there is no error and at some point the importing doesn't progress

Try to import a VM with 100GB disk (66% usage), while CNV PSI based environment worker disk size was 40GB.
The import did not end normally.
After ~ 2 hours run, the progress stopped ~49% (displayed in VM annotation),
and then VM continued to be in state importing, however by the conversion pod log, no data transfer was seen anymore.

I deleted the VM (while in importing state), 
then tried to do a small RHEL-7 VM (10GB disk) import. VM importing it was pending.
The related PVs/PVCs were also in pending state, and it remained in this state for a long time.
After ~10 minutes, I deleted the PVCs and PVs, that were related to the VM with large disk.
That didn't made the "pending" PVs/PVCs/importing of the small RHEL VM proceed.

Removing all VMs/PVs/PVCs also didn't solve the issue.
Deleting the v2v-vmware pod also didn't resolve the issue.
Eventually had to redeploy the CNV environment. 

Version-Release number of selected component (if applicable):
CNV-2.2.0-10

Marking as regression as in CNV 2.0 the behavior was that the import of a VM with a larger disk failed, and did not prevent from running further VM imports with disks with suitable size.