Created attachment 1647490 [details] Bug conversion log Description of problem: While trying to import VM from VMware to CNV with disk size that bigger than the available storage space in the cluster - there is no error in the Events page, the importing is started and at some point gets stuck Version-Release number of selected component (if applicable): CNV 2.2.0-10 How reproducible: 100% Steps to Reproduce: Migrate VM (vmware -> cnv) who has larger disk size then the available space in cluster Actual results: There is no error and at some point the importing doesn't progress Expected results: The importing won't be started OR will fail with a relevant error message in the Events page Please see BZ bug: https://bugzilla.redhat.com/show_bug.cgi?id=1721504 Additional info: The import has been running for 2.5 hours (after it we stopped the import). In the saved log - it seems that after 2 hours run it stopped reading disk, and instead in the log there are repeated messages: 2019-12-24 07:25:06,611 - root - DEBUG - Accessing Kubernetes on: https://172.30.0.1:443/api/v1/namespaces/default/pods/kubevirt-v2v-conversion-vm-100gb-bclln 2019-12-24 07:25:06,622 - root - DEBUG - HTTP response code 200 2019-12-24 07:25:06,622 - root - DEBUG - Updating progress in POD annotation Attached: conversion log
Additional info (CNV v2.2.0-10): It is not possible to import VM on the environment after bug reproduction. Delete the "importing" VM (by conversion log and annotation, the import is stuck) -> delete its PVCs/PVs -> run another import -> 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)"
Opened bug regarding the scenario described in comment #1: https://bugzilla.redhat.com/show_bug.cgi?id=1786330
Closing this in lieu of the *** This bug has been marked as a duplicate of bug 1721504 ***