-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.17
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
When a VolumeSnapshot is created from a PersistentVolumeClaim (PVC), the OpenShift Console allows users to restore the snapshot only while the original (parent) PVC still exists.
Once the parent PVC is deleted, the "Restore" option in the Console becomes disabled, preventing users from restoring the snapshot through the UI. However, it is still possible to manually restore the snapshot using the CLI by creating a new PVC with the snapshot as a dataSource.
This inconsistency between the Console and CLI behavior leads to confusion and limits usability for users relying solely on the UI.
The underlying reason for this behavior in the OpenShift Console is unclear.
1. Create a volumesnapshot from the PVC. 2. Delete the parent PVC. 3. Try to restore the snapshot from the console. 4. Noticed that the restore option is disbaled. 5. Restored the snapshot via CLI using a new PVC YAMl manifests. ~~~ apiVersion: v1 kind: PersistentVolumeClaim metadata: name: restore-pvc spec: storageClassName: <Storage-class-used-parent-pvc> dataSource: name: <volume-snapshot-name> kind: VolumeSnapshot apiGroup: snapshot.storage.k8s.io accessModes: - ReadWriteOnce resources: requests: storage: <size> ~~~ 6. Verified that the restored PVC is created and the data is accessible.
Expected results
The restore option should remain available in the openshift console, even if the parent pvc is deleted. Users should be able to restore a new PVC from a volumesnapshot via the console after deleting the parent PVC, as worked by CLI.
