Bug 1857786

Summary:	[v2v][Doc][RHV to CNV VM import] Please fail VM import in case there is no available suitable storage
Product:	Container Native Virtualization (CNV)	Reporter:	Ilanit Stein <istein>
Component:	Documentation	Assignee:	Avital Pinnick <apinnick>
Status:	CLOSED NEXTRELEASE	QA Contact:	Ilanit Stein <istein>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.4.0	CC:	apinnick, cnv-qe-bugs, ncredi, pkliczew
Target Milestone:	---
Target Release:	2.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	2.4.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1857784	Environment:
Last Closed:	2020-07-21 14:01:12 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1857784
Bug Blocks:

Description Ilanit Stein 2020-07-16 15:00:11 UTC

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

Comment 2 Ilanit Stein 2020-07-19 21:21:10 UTC

@Avital,
I could not find in the trouble shooting section that a case of being stuck in VM import on 10%, and the details on what might have caused this.

Comment 3 Ilanit Stein 2020-07-19 21:29:09 UTC

Also please check original bug last comments, or more info on what needs to be documented.