Description of problem: It is not possible to delete a PVC created using a data upload. It will reappear again. Actual results: Upload something into a PVC. Try to delete it. It will re-appear. Expected results: It will actually be deleted (e.g. the datavolume behind it should be deleted) Additional info:
@Matt: we have couple of options here: 1: the delete PVC would detect that this PVC is backed by a datavolume and would delete the datavolume instead (e.g. it would be for the user a seamless experience, he wants to delete a PVC and it gets deleted nvm how) 2: the delete PVC would warn the user that this is backed by a datavolume and deleting it means it will get re-created again (I dont think this is any useful though...) 3: letting the user know that this PVC is backed by a datavolume so the datavolume will be deleted instead and than delete the datavolume (e.g. similar to the first one but letting the user know what is actually going on) @Matt: wdyt?
I think option 3 is best. It would be good to inform the user the PVC and it’s backing data volume will be deleted.
It shows a warning "Deleting this PVC will also delete upload-cirros Data Volume" while deleting PVC backed by dv.
golden pvc detection changed, need to fix this bug again
have to move out of 4.6 blocker list but definitely want to fix asap
verified on master UI, delete pvc and golden pvc successfully
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 (OpenShift Container Platform 4.6 GA Images), 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/RHBA-2020:4196