-
Bug
-
Resolution: Duplicate
-
None
-
None
-
False
-
-
False
-
NEW
-
---
-
---
-
Medium
-
None
Description of problem:
When VM creation fails during the cloning procedure, deletion of the VM would delete the DataVolume, but the cdi-tmp-* PVC that was created during the procedure remains.
Version-Release number of selected component (if applicable):
OpenShift 4.10.16
OpenShift Virtualization 4.10.1
How reproducible:
Always
Steps to Reproduce:
1. The source disk is in a PVC in the openshift-virtualization-os-images namespace and uses a Ceph storage class.
2. The creation of the VM in a different namespace fails during the cloning procedure.
3. After the failure, the DataVolume is deleted.
Actual results:
In the source namespace openshift-virtualization-os-images there's a leftover cdi-tmp-* PVC that it's stuck in "Pending" state.
Expected results:
The cdi-tmp-* PVC is removed too.
Additional info:
This looks like the same issue reported in these links, which in theory was fixed in 4.8.1:
https://bugzilla.redhat.com/show_bug.cgi?id=1994504
https://github.com/kubevirt/containerized-data-importer/issues/2323
- duplicates
-
CNV-19470 [2102180] [4.10.z]Smart clone and csi clone leaves tmp unbound PVC and ObjectTransfer
- Closed
- external trackers