-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
0.42
-
False
-
-
False
-
None
-
-
None
following bug https://issues.redhat.com/browse/CNV-57559
I recognized that cdi does not clean datavolume resources when user fails to add/ upload datavolume
you can try to do that by executing following
notice (you can download image for example from https://mirror.openshift.com/pub/openshift-v4/x86_64/dependencies/rhcos/latest/)
virtctl image-upload dv test-qcow2 --namespace default --image-path=./test-82g.qcow2 --insecure --uploadproxy-url=https://cdi-uploadproxy-openshift-cnv.apps.iuo-ahmad419.rhos-psi.cnv-qe.rhood.us --wait-secs=600 --access-mode=ReadWriteOnce --storage-class=ocs-storagecluster-ceph-rbd --size=30Gi Using existing PVC default/prime-0f78ba52-a77f-40dc-975b-48d763197891 Uploading data to https://cdi-uploadproxy-openshift-cnv.apps.iuo-ahmad419.rhos-psi.cnv-qe.rhood.us
the upload will be failing
966.41 KiB / 193.28 KiB [----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------] 500.00% 652.37 KiB p/s 1.7s
error uploading image after 5 retries: unexpected return value 400, Saving stream failed: effective image size is larger than the reported available storage. A larger PVC is required
now the question is
are those resources need to be cleaned-up since the datavolume upload (by user) fails?
[cloud-user@ocp-psi-executor-xl ahmad]$ oc get dv NAME PHASE PROGRESS RESTARTS AGE test-qcow2 UploadReady N/A 16m [cloud-user@ocp-psi-executor-xl ahmad]$ oc get pvc NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS VOLUMEATTRIBUTESCLASS AGE prime-0f78ba52-a77f-40dc-975b-48d763197891 Bound pvc-0a217a37-bce3-41d3-907a-4843a7d62c0d 30Gi RWO ocs-storagecluster-ceph-rbd <unset> 16m prime-0f78ba52-a77f-40dc-975b-48d763197891-scratch Bound pvc-7b0aa686-6d93-44ff-b768-9627edf139df 149Gi RWO hostpath-csi-basic <unset> 16m test-qcow2 Pending ocs-storagecluster-ceph-rbd <unset> 16m [cloud-user@ocp-psi-executor-xl ahmad]$ oc get pods NAME READY STATUS RESTARTS AGE cdi-upload-prime-0f78ba52-a77f-40dc-975b-48d763197891 1/1 Running 0 16m
rh-ee-aaloni skagan@redhat.com rhn-support-awels alitke@redhat.com rhn-support-mrobson please share you inputs regard this, and if this behavior is going to be changed
- is related to
-
CNV-57559 Add volume with too small of a disk fails with status code 400 and leaves resources behind
-
- Verified
-
