dove-young
commented
3 months ago Here are what I did
[root@api.o1-726938]# velero backup get test-backup
NAME STATUS ERRORS WARNINGS CREATED EXPIRES STORAGE LOCATION SELECTOR
test-backup Completed 0 0 2024-04-11 20:30:39 -0700 PDT 29d default <none>
[root@api.o1-726938]#
[root@api.o1-726938]# velero restore describe test-backup-20240411204147
Name: test-backup-20240411204147
Namespace: velero
Labels: <none>
Annotations: <none>
Phase: Failed (run 'velero restore logs test-backup-20240411204147' for more information)
Total items to be restored: 7848
Items restored: 400
Started: 2024-04-11 20:41:47 -0700 PDT
Completed: 2024-04-11 20:43:09 -0700 PDT
Backup: test-backup
Namespaces:
Included: all namespaces found in the backup
Excluded: <none>
Resources:
Included: *
Excluded: nodes, events, events.events.k8s.io, backups.velero.io, restores.velero.io, resticrepositories.velero.io, csinodes.storage.k8s.io, volumeattachments.storage.k8s.io, backuprepositories.velero.io
Cluster-scoped: auto
Namespace mappings: <none>
Label selector: <none>
Or label selector: <none>
Restore PVs: auto
Existing Resource Policy: <none>
ItemOperationTimeout: 4h0m0s
Preserve Service NodePorts: auto
[root@api.o1-726938]#
[root@api.o1-726938]# velero backup describe test-backup
Name: test-backup
Namespace: velero
Labels: velero.io/storage-location=default
Annotations: velero.io/resource-timeout=10m0s
velero.io/source-cluster-k8s-gitversion=v1.28.7+f1b5f6c
velero.io/source-cluster-k8s-major-version=1
velero.io/source-cluster-k8s-minor-version=28
Phase: Completed
Namespaces:
Included: *
Excluded: <none>
Resources:
Included: *
Excluded: <none>
Cluster-scoped: auto
Label selector: <none>
Or label selector: <none>
Storage Location: default
Velero-Native Snapshot PVs: auto
Snapshot Move Data: false
Data Mover: velero
TTL: 720h0m0s
CSISnapshotTimeout: 10m0s
ItemOperationTimeout: 4h0m0s
Hooks: <none>
Backup Format Version: 1.1.0
Started: 2024-04-11 20:30:39 -0700 PDT
Completed: 2024-04-11 20:32:05 -0700 PDT
Expiration: 2024-05-11 20:30:39 -0700 PDT
Total items to be backed up: 8983
Items backed up: 8983
Backup Volumes:
Velero-Native Snapshots: <none included>
CSI Snapshots: <none included>
Pod Volume Backups: <none included>
HooksAttempted: 0
HooksFailed: 0
[root@api.o1-726938]#
sseago
github-actions[bot]
What steps did you take and what happened:
I restored a backup from OCP cluster to another OCP cluster, the restore failed after a few moment. My storage is Minio
I checked
velero restore logs, it saidAn error occurred: file not foundWhat did you expect to happen:
restore will finish success
The following information will help us better understand what's going on:
bundle-2024-04-11-20-51-32.tar.gz
If you are using velero v1.7.0+:
Please use
velero debug --backup <backupname> --restore <restorename>to generate the support bundle, and attach to this issue, more options please refer tovelero debug --helpIf you are using earlier versions:
Please provide the output of the following commands (Pasting long output into a GitHub gist or other pastebin is fine.)
kubectl logs deployment/velero -n velerovelero backup describe <backupname>orkubectl get backup/<backupname> -n velero -o yamlvelero backup logs <backupname>velero restore describe <restorename>orkubectl get restore/<restorename> -n velero -o yamlvelero restore logs <restorename>Anything else you would like to add:
Environment:
velero version): v1.13.1velero client config get features): features:kubectl version): Client Version: v1.28.2 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.28.7+6e2789b/etc/os-release): RHEL 8Vote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.