Description of problem:
DV/PVC is created anyway when 'Data Volume failed to initiate upload' shows on UI.
$ oc get dv
NAME PHASE PROGRESS RESTARTS AGE
fedora32 UploadScheduled N/A 4m11s
$ oc get pvc
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
fedora32 Bound pvc-e592c682-214c-4a94-a265-819cdd4ca942 100Gi RWO standard 5m46s
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. fill a very large pvc size and start upload
fails with error `Data Volume failed to initiate upload`, and dv/pvc is created.
once an error occurrs, the dv/pvc should not be created.
That is actually correct. The API is that we initiate the import by creating the DV which creates the PVC and than starts uploading into it.
And CDI is eventually consistent which means that even if it fails, it does not consider it to be a failure but keeps trying hoping that it will work out one day.
So Im afraid we can not fix this
I think customer will have the same question one day, so filed a bug here.