Details
-
Bug
-
Resolution: Done
-
Blocker
-
OADP 1.1.1
-
False
-
-
False
-
oadp-volume-snapshot-mover-container-1.1.1-25
-
Passed
-
No
-
0
-
0
-
Very Likely
-
0
-
None
-
Unset
-
Unknown
Description
Description of problem:
DataMover backup failed with error "cannot obtain source volumesnapshot" after setting the timeout in DPA CR.
I have also encountered the same issue with MGC bucket.
https://coreos.slack.com/archives/C0144ECKUJ0/p1665751004189709
Version-Release number of selected component (if applicable):
OADP 1.1.1 (1.1.1-38)
OSP 4.11
How reproducible:
Intermittent
Steps to Reproduce:
1. Create a DPA CR with dataMover timeout set as 10s
apiVersion: oadp.openshift.io/v1alpha1 kind: DataProtectionApplication metadata: namespace: openshift-adp name: example-velero spec: configuration: velero: defaultPlugins: - openshift - aws - csi restic: enable: true backupLocations: - name: default velero: provider: aws default: true objectStorage: bucket: oadpbucket153821 prefix: velero config: profile: default region: us-east-2 credential: name: cloud-credentials key: cloud features: dataMover: enable: true timeout: 10s
2. Create a backup
Actual results:
VSB failed with error "cannot obtain source volumesnapshot"
$ oc get vsb -n ocp-attached-pvc vsb-ctk7s -o yaml status: conditions: lastTransitionTime: "2022-11-08T11:50:18Z" message: cannot obtain source volumesnapshot ocp-attached-pvc/velero-test-data-ntkqs reason: Error status: "False" type: Reconciled phase: PartiallyFailed sourcePVCData: {} volumeSnapshotClassName: ocs-storagecluster-rbdplugin-velero Expected results: VSB should not fail with error "cannot obtain source volumesnapshot"
Additional info: