-
Sub-task
-
Resolution: Not a Bug
-
Undefined
-
None
-
None
-
None
-
None
-
False
-
-
False
-
ToDo
-
-
-
0
-
0
-
Very Likely
-
0
-
None
-
Unset
-
Unknown
Description of problem:
PodVolumeRestore are not created for PodVolumeBackup with empty volume using Restic
I see that backup and restore are successful. There are 4 podvolumebackups created out of which 2 have following status
status: completionTimestamp: "2024-02-07T11:12:21Z" message: volume was empty so no snapshot was taken path: /host_pods/e7444087-ff8c-4a1b-aba2-d4fe214ac189/volumes/kubernetes.io~csi/pvc-1a1cb1f3-7866-477f-91b4-cf185177bd97/mount phase: Completed progress: {} startTimestamp: "2024-02-07T11:12:20Z"
Other 2 PodVolumeBackup have following status
status: completionTimestamp: "2024-02-07T11:11:23Z" path: /host_pods/e7444087-ff8c-4a1b-aba2-d4fe214ac189/volumes/kubernetes.io~csi/pvc-b1196dbd-a743-4c59-ad7c-b623fa24f567/mount phase: Completed progress: bytesDone: 107855491 totalBytes: 107855491 snapshotID: d4239b7b startTimestamp: "2024-02-07T11:11:18Z"
There are only 2 PodVolumeRestore getting created
Storage class used is ocs-storagecluster-cephfs
Version-Release number of selected component (if applicable):
1.3.1
How reproducible:
Steps to Reproduce:
1. Follow these Polarian steps - https://polarion.engineering.redhat.com/polarion/redirect/project/OADP/workitem?id=OADP-266
2. Check whether number of PodVolumeBackup equals PodVolumeRestore
Actual results:
Number of PodVolumeBackup does not matches with the number of PodVolumeRestores
Expected results:
Number of PodVolumeBackup should match with the number of PodVolumeRestores
Additional info: