+++ This bug was initially created as a clone of Bug #2203278 +++ Description of problem: When doing a snapshot clone, the part of the code that creates a PVC with the snapshot source currently relies on the restoreSize of the VolumeSnapshot. If this value is 0 then creating the PVC fails (because we are attempting to create a 0 size PVC). For various reasons it might not be feasible to get a proper value in this field by the driver. See: democratic-csi/democratic-csi#129 We do know ahead of time what we want the size of the PVC to be, but due to some older broken CSI drivers we had to start at the restoreSize and then expand to the target size. If we consider that behavior (target PVC size must equal restore size) a bug in the CSI driver, then we can create a PVC of the requested size regardless of the restoreSize in the snapshot. Version-Release number of selected component (if applicable): How reproducible: Use a CSI driver that has this issue (like the democratic-csi, or dell storage). Steps to Reproduce: 1. Try to create a snapshot clone 2. Clone will remain stuck in snapshot in progress. 3. Actual results: No clone happens Expected results: Clone happens normally even with storage where the restoreSize of the snapshot is 0. Additional info:
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 Virtualization 4.13.1 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/RHEA-2023:3686