-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Closed
Labels
Needs infoWaiting for informationWaiting for information
Description
Using velero with gcp bucket.
Upgraded:
velero: 1.16.2 -> 1.17.0
velero-plugin-for-gcp: 1.12.2 -> 1.13.0
example backup:
velero backup create test-ns-$(date +%Y%m%d%H%M%S) --ttl=72h --include-resources pvc,pv --snapshot-move-data=true --include-namespaces test
Backups failing immediately with:
Phase: Failed (run `velero backup logs test-ns-20251016115526` for more information)
% velero backup logs test-ns-20251016115526
An error occurred: file not found
Status:
Completion Timestamp: 2025-10-16T09:55:27Z
Expiration: 2025-10-19T09:55:27Z
Failure Reason: error checking if backup already exists in object storage: rpc error: code = Unknown desc = storage: object doesn't exist: googleapi: Error 404: No such object: velero/staging/backups/test-ns-20251016115526/velero-backup.json, notFound
Format Version: 1.1.0
Phase: Failed
Start Timestamp: 2025-10-16T09:55:27Z
Version: 1
Events: <none>
After plugin downgrade:
velero-plugin-for-gcp: 1.13.0 -> 1.12.2
Working again
Looks related to: vmware-tanzu/velero-plugin-for-gcp#239
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Needs infoWaiting for informationWaiting for information