Description of problem:
The error below (received in the conversion pod events) indicates 2 issues:
1. When there are no available PVs -> required action: deleting PVCs
2. When trying to import VM with disk size larger than the available space in the cluster. E.g. importing 100gb VM when the PVs capacity is 25gb -> will never work
"0/3 nodes are available: 1 node(s) had taints that the pod didn't tolerate, 1 node(s) had volume node affinity conflict, 2 node(s) didn't find available persistent volumes to bind"
We want to avoid this error by adding validation that will check if there is available storage in the cluster, in order to execute the VM migration
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Migrate VM that has disk size larger than the available space in the cluster
Update regarding CNV v2.2.0-10:
Importing Large disk cause no errors, the conversion log doesn't show disk copy, and the import progress gets stuck
BZ bug: https://bugzilla.redhat.com/show_bug.cgi?id=1786293
*** Bug 1786293 has been marked as a duplicate of this bug. ***
Once vmware would get moved to vm-import-controller we can handled this case as described in BZ #1858595. I think we can close this one as won't fix.
@Brett what do you think?
(In reply to Piotr Kliczewski from comment #6)
> Once vmware would get moved to vm-import-controller we can handled this case
> as described in BZ #1858595. I think we can close this one as won't fix.
> @Brett what do you think?
OK to close as a duplicate.
*** This bug has been marked as a duplicate of bug 1858595 ***