Bug 1786330 - [DOC] [v2v] Unable to import VM after import of a large disk using rook-ceph storage
Summary: [DOC] [v2v] Unable to import VM after import of a large disk using rook-ceph ...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Documentation
Version: 2.2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 2.2.0
Assignee: Avital Pinnick
QA Contact: Maayan Hadasi
URL:
Whiteboard:
: 1786355 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-24 13:23 UTC by Maayan Hadasi
Modified: 2020-01-27 08:53 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
Text added to import prerequisites: * There must be sufficient storage space for the imported disk. + [WARNING] ==== If you try to import a virtual machine whose disk size is larger than the available storage space, the operation will not complete. You will not be able to import another virtual machine or to delete PVCs or PVs because the Ceph storage will not have sufficient resources for object deletion. You must add more Ceph OSDs to clean up the storage. ====
Clone Of:
Environment:
Last Closed: 2020-01-26 09:42:25 UTC
Target Upstream Version:
Embargoed:
mguetta: needinfo+
mguetta: needinfo+
apinnick: needinfo-
apinnick: needinfo+
istein: needinfo+

Attachments (Terms of Use)

Description Maayan Hadasi 2019-12-24 13:23:08 UTC 
Description of problem:
It is not possible to import VM on the CNV environment after reproduction of bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1786293 - [v2v] Large disk - there is no error and at some point the importing doesn't progress


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


How reproducible:
1/1 

Steps to Reproduce:
1. Migrate VM (vmware -> cnv) who has disk size bigger than the available storage in cluster
2. This bug occurs: Large disk - there is no error and at some point the importing doesn't progress (the import is not ended normally)
3. Delete the VM and the related PV/Cs
4. Import a small VM


Actual results:
The small VM, PVCs and conversion pod status is pending, and the VM Events page shows this error message:
"pod has unbound immediate PersistentVolumeClaims (repeated 3 times)"


Additional info:
Tried to restart the vmware-v2v pod - didn't help.
The environment were redeployed
Comment 1 Ilanit Stein 2019-12-24 16:05:54 UTC 
*** Bug 1786355 has been marked as a duplicate of this bug. ***
Comment 12 Ric Garcia 2020-01-13 15:28:43 UTC 
Blocker flag not requested, pushing to CNV 2.3.
Comment 16 Maayan Hadasi 2020-01-15 08:52:05 UTC 
Turned this issue into a doc bug, since it's the expected behavior of the backend rook-ceph storage
Comment 20 Nelly Credi 2020-01-15 15:09:38 UTC 
i see this is targeted to 2.3, but it is a verified doc bug
should it move back to 2.2?
and please add acks
Comment 23 Avital Pinnick 2020-01-26 09:42:25 UTC 
Merged.
Note You need to log in before you can comment on or make changes to this bug.