Description of problem: Smart-clone and CSI clone across namespace leaves orphan unbound PVC in source namespace. Also, the corresponding ObjectTransfer resource is not deleted until the target DataVolume is deleted. This issue was originally submitted in github here: https://github.com/kubevirt/containerized-data-importer/issues/2323 Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Create DataVolume in namespace A populated by http import 2. Clone above DataVolume to Namespace B Actual results: There is a tmp unbound PVC in namespace A There is completed ObjectTransfer Expected results: No unexpected resources Additional info: https://github.com/kubevirt/containerized-data-importer/issues/2323
Waiting ~24h to see what cpaas automation is going to do with this if anything. A downstream version containing this fix is CNV v4.11.0-547.
Test on CNV v4.11.0-552, issue has been fixed. $ oc get dv -n golden NAME PHASE PROGRESS RESTARTS AGE golden-centos-dv Succeeded 100.0% 1 13m $ oc get dv -n customer1 NAME PHASE PROGRESS RESTARTS AGE clone-centos-dv-customer1 Succeeded N/A 7m6s $ oc get pvc -n golden NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE golden-centos-dv Bound pvc-62f7cbd3-7e84-4f09-8a50-7133ef722b71 10Gi RWO ocs-storagecluster-ceph-rbd 13m $ oc get pvc -n customer1 NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE clone-centos-dv-customer1 Bound pvc-e8a0538d-e883-4752-ac38-0adcd643b08b 10Gi RWO ocs-storagecluster-ceph-rbd 7m32s $ oc get pv pvc-62f7cbd3-7e84-4f09-8a50-7133ef722b71 10Gi RWO Delete Bound golden/golden-centos-dv ocs-storagecluster-ceph-rbd 13m pvc-e8a0538d-e883-4752-ac38-0adcd643b08b 10Gi RWO Delete Bound customer1/clone-centos-dv-customer1 ocs-storagecluster-ceph-rbd 7m45s
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Virtualization 4.11.0 Images security and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:6526