-
Bug
-
Resolution: Done
-
Major
-
None
-
False
-
-
False
-
ToDo
-
0
-
0
-
Very Likely
-
0
-
None
-
Unset
-
Unknown
-
No
Description of problem:
If a backup using data mover is running with ODF/noobaa bsl, the volsync pod will error and continuously re-create.
How reproducible:
100%
Steps to Reproduce:
1. enable data mover with a ODF/noobaa bsl
2. run a backup
3. oc get po n openshiftadp | grep volsync
Actual results:
error in volsync pod:
ERROR: failure checking existence of repository
~ $ oc get po -n openshift-adp
NAME READY STATUS RESTARTS AGE
39f1f7d1f60dfc4d31865487897864ec992fa9f5ff50a885150c845265qdlhc 0/1 Completed 0 14m
openshift-adp-controller-manager-5445fdcb85-mf42r 1/1 Running 0 13m
ttl-sh-oadp-operator-bundle-7d36ab0-1h 1/1 Running 0 14m
velero-ddd67bb8b-9k6xn 1/1 Running 0 7m9s
volsync-src-vsb-velero-rocketchat-data-claim-hgjnm-rep-src777qj 0/1 ContainerCreating 0 2s
volsync-src-vsb-velero-rocketchat-data-claim-hgjnm-rep-src7x6kd 0/1 Error 0 18s
volsync-src-vsb-velero-rocketchat-data-claim-hgjnm-rep-srcbfn8l 0/1 Error 0 8s
volsync-src-vsb-velero-rocketchat-data-claim-hgjnm-rep-srccmldt 0/1 Error 0 14s
volsync-src-vsb-velero-rocketchat-data-claim-hgjnm-rep-srcqfd5t 0/1 Error 0 11s
volsync-src-vsb-velero-rocketchat-data-claim-hgjnm-rep-srczzjw4 0/1 Error 0 5s
volume-snapshot-mover-676588c84c-ljqhl 1/1 Running 0 7m9s
Expected results:
successful data mover backup.
