-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
OADP 1.4.4
-
None
-
Incidents & Support
-
3
-
False
-
-
False
-
ToDo
-
-
-
Very Likely
-
0
-
None
-
Unset
-
Unknown
-
None
Environment:
OCP 4.16 with OADP 1.4.4.
BSL is a noobaa (odf) s3 bucket.
Customer is retrieving errors on the Noobaa endpoint as some Velero/kopia process is trying to access the ${bucket}/velero/kopia/${backuprepository}/. storageconfig file, which it doesn't exist.
Need to investigate:
- Why and when velero/kopia is attempting to access this file?
- If the file exists or not
- In case of yes, why has it not been created during repo init?
- In case of no, why is being accessed?