Description of problem: When cloning an nfs DV with a target size that is bigger than the source, clone does not progress Version-Release number of selected component (if applicable): CNV 4.9.0 How reproducible: 100% Steps to Reproduce: 1. Clone nfs DV (manifests below) Actual results: NAMESPACE NAME PHASE PROGRESS RESTARTS AGE default dv-target 3s "level":"error","ts":1630407986.6950176,"logger":"controller-runtime.manager.controller.datavolume-controller","msg":"Reconciler error","name":"dv-target","namespace":"default","error":"source/target sizes not compatible" Expected results: DV Succeeded Additional info: - In 4.8 this operation succeeds - Are we ok with looping over https://github.com/kubevirt/containerized-data-importer/blob/main/pkg/controller/datavolume-controller.go#L1558-L1560 indefinitely (it's part of advancedClonePossible check)? shouldn't we just fail here and go to host assisted? - The only indication of error is in cdi-deployment logs - When reproducing, keep in mind that the nfs pvc.Status.Capacity can be bigger than your request in the DV [cnv-qe-jenkins@alex490-143-szbxl-executor clone-nfs-loop]$ cat dv_source.yaml apiVersion: cdi.kubevirt.io/v1beta1 kind: DataVolume metadata: name: dv-source namespace: openshift-virtualization-os-images spec: source: http: url: "http://.../rhel-84.qcow2" pvc: storageClassName: nfs namespace: default accessModes: - ReadWriteOnce resources: requests: storage: 25Gi [cnv-qe-jenkins@alex490-143-szbxl-executor clone-nfs-loop]$ cat dv_target.yaml apiVersion: cdi.kubevirt.io/v1beta1 kind: DataVolume metadata: name: dv-target namespace: default spec: pvc: storageClassName: nfs accessModes: - ReadWriteOnce resources: requests: storage: 26Gi source: pvc: name: dv-source namespace: openshift-virtualization-os-images
I am going to propose blocker+ for this bug. Michael, do we have a PR or plan to fix this? Could you attach?
Test on latest CNV - CNV-v4.9.0-220, issue has been fixed $ oc get dv NAME PHASE PROGRESS RESTARTS AGE dv-target CloneInProgress 0.00% 25s $ oc get dv NAME PHASE PROGRESS RESTARTS AGE dv-target Succeeded 100.0% 6m
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 (Moderate: OpenShift Virtualization 4.9.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-2021:4104