-
Bug
-
Resolution: Won't Do
-
Normal
-
OADP 1.1.0
-
1
-
False
-
-
False
-
ToDo
-
0
-
0.000
-
Very Likely
-
0
-
None
-
Unset
-
Unknown
-
No
Description of problem: Django app backup fails with the following error:
velero failure logs: [velero container error line#126: time="2022-07-31T15:12:50Z" level=error msg="Current BackupStorageLocations available/unavailable/unknown: 0/0/1)" controller=backup-storage-location logSource="pkg/controller/backup_storage_location_controller.go:173" 07-31 18:21:08.443 velero container error line#1811: time="2022-07-31T15:20:41Z" level=error msg="Namespace django-persistent, resource restore error: error preparing imagestreams.image.openshift.io/django-persistent/django-psql-persistent: rpc error: code = Unknown desc = reading config blob sha256:d3a7ed66f3f2e871ee02a61390b773a10293a51b2ecaea6bf1c63d1340f98dcd: Error fetching blob: invalid status code from registry 403 (Forbidden)" logSource="pkg/controller/restore_controller.go:504" restore=openshift-adp/django-persistent-2c81526e-10e3-11ed-a57b-0a58ac1e0830 07-31 18:21:08.443 ]
This is a regression, as it passed few builds ago:
not sure if related to https://issues.redhat.com/browse/OADP-552 as it happens with CSI and restic (haven't checked with VSL yet), so opened a new bug.
Version-Release number of selected component (if applicable): 1.1.0-50
How reproducible: 100%
Steps to Reproduce:
1. Create a backup of the Django app and check it's status when completed
Actual results:
Expected results:
Additional info:
Tiger Notes: This bug came up when S3_URL contained port after this change
which sets custom s3 url for aws plugin to `{{ S3_URL=http://s3.openshift-storage.svc.cluster.local:80}}`
- relates to
-
-
- Closed
-
-
-
- Closed
-
- links to
- mentioned on
