Merge pull request #56408 from subhtk/BZ2094494

BZ#2094494: Added a section titled 'Backup CR status remains in PartiallyFailed'

Author: mjpytlak

modules/oadp-backup-restore-cr-issues.adoc

@@ -51,3 +51,37 @@ $ oc delete backup <backup> -n openshift-adp
 You do not need to clean up the backup location because a `Backup` CR in progress has not uploaded  files to object storage.
 
 . Create a new `Backup` CR.
+
+[id="backup-cr-remains-partiallyfailed_{context}"]
+== Backup CR status remains in PartiallyFailed
+
+The status of a `Backup` CR without Restic in use remains in the `PartiallyFailed` phase and does not complete. A snapshot of the affiliated PVC is not created. 
+
+.Cause
+
+If the backup is created based on the CSI snapshot class, but the label is missing, CSI snapshot plugin fails to create a snapshot. As a result, the `Velero` pod logs an error similar to the following:
++
+[source,text]
+----
+time="2023-02-17T16:33:13Z" level=error msg="Error backing up item" backup=openshift-adp/user1-backup-check5 error="error executing custom action (groupResource=persistentvolumeclaims, namespace=busy1, name=pvc1-user1): rpc error: code = Unknown desc = failed to get volumesnapshotclass for storageclass ocs-storagecluster-ceph-rbd: failed to get volumesnapshotclass for provisioner openshift-storage.rbd.csi.ceph.com, ensure that the desired volumesnapshot class has the velero.io/csi-volumesnapshot-class label" logSource="/remote-source/velero/app/pkg/backup/backup.go:417" name=busybox-79799557b5-vprq
+----
+
+.Solution
+
+. Delete the `Backup` CR:
++
+[source,terminal]
+----
+$ oc delete backup <backup> -n openshift-adp
+----
+
+. If required, clean up the stored data on the `BackupStorageLocation` to free up space.
+
+. Apply label `velero.io/csi-volumesnapshot-class=true` to the `VolumeSnapshotClass` object:
++
+[source,terminal]
+----
+$ oc label volumesnapshotclass/<snapclass_name> velero.io/csi-volumesnapshot-class=true
+----
+
+. Create a new `Backup` CR.