Bug 1721504

Summary:	[V2V] [RFE] Adding validation to check available cluster storage
Product:	Container Native Virtualization (CNV)	Reporter:	Maayan Hadasi <mguetta>
Component:	V2V	Assignee:	Brett Thurber <bthurber>
Status:	CLOSED DUPLICATE	QA Contact:	Maayan Hadasi <mguetta>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.0	CC:	bthurber, cnv-qe-bugs, dagur, ibragins, istein, pkliczew, tjelinek
Target Milestone:	---
Target Release:	future
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-07-31 13:43:29 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 Maayan Hadasi 2019-06-18 12:42:30 UTC

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

Error message:
"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):
HCO_BUNDLE_REGISTRY_TAG: 	


Steps to Reproduce:
1. Migrate VM that has disk size larger than the available space in the cluster

Comment 2 Maayan Hadasi 2019-12-24 09:31:09 UTC

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

Comment 3 Brett Thurber 2020-01-08 04:13:01 UTC

*** Bug 1786293 has been marked as a duplicate of this bug. ***

Comment 6 Piotr Kliczewski 2020-07-30 09:33:03 UTC

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?

Comment 7 Brett Thurber 2020-07-31 13:43:29 UTC

(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 ***