As the below original bug will not be fixed in CNV-2.4,
Need to add to docs /troubleshooting section, that if the VM import is stack @10% - need to check the storage PVC binding, to see if it is a problem of not allocating the suitable storage for the disks import.

+++ This bug was initially created as a clone of Bug #1857784 +++

Description of problem:
When running VM import, and there is no storage PV that should fit the import needs. the VM import will stay forever in a state o "Importing", with showing progress bar stack on 10%.

VM event do not indicate what is the problem.

Navigating to pods - seeing that the importer pod is in pending state,
and it's event show:
"Failed to bind volumes: provisioning failed for PVC "rhel7-vm-9f242f97-38df-42e9-9489-ae975c0e0383"

Cases of not being able to allocate storage:
1. This case happen to me when I tried to VM import using "Standard" Cinder storage, that was picked by default, since I haven't set target storage to any storage class.

2. Another case was on bere metal CNV, where the ceph storage had almost reached out of space (reached it's limit becoming not able to be used anymore)

Please fail the MV import in such cases, to indicate to the user what is the cause of having the VM import not being able to perform.

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