reasonerjt
commented
2 years ago @chrislinan Have you tried manually run the backup (not via schedule)?
Based on the information you provided it's hard to tell if it's due to error in calling Azure's API
We need more logs to debug.
As for the error by velero debug, it should by default looking for velero deployment in ns velero not default. You may also customize the namespace by using --namespace in the command, check velero debug --help
Additionally, are you using a released? The commit ID should NOT be dev.
chrislinan
ywk253100
What steps did you take and what happened: I create a backup from schedule, and velero log shows everythings gose well but the back up failed in the end. log: time="2022-05-08T14:10:54Z" level=error msg="backup failed" controller=backup error="rpc error: code = Unavailable desc = error reading from server: EOF" key=default/velero-backup-obj-3f6fffe7-867b-4609-bade-00e5ab32977d logSource="pkg/controller/backup_controller.go:282"
What did you expect to happen: backup succeeded
The following information will help us better understand what's going on:
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 --helpAn error occurred: velero deployment does not exist in namespace: defaultIf 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 yamlName: velero-backup-obj-a9badd03-192e-4123-8b92-ea5476d7bf84 Namespace: default Labels: app.kubernetes.io/name=velero helm.sh/chart=hc-disaster-recovery-2.9.15 velero.io/schedule-name=velero-backup-obj velero.io/storage-location=default Annotations: kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"velero.io/v1","kind":"Schedule","metadata":{"annotations":{},"labels":{"app.kubernetes.io/name":"velero","helm.sh/chart":"hc-disaster-recovery-2.9.15"},"name":"velero-backup-obj","namespace":"default"},"spec":{"schedule":"0 0 0 0 0","template":{"excludedNamespaces":["kube-system","kube-public","kube-node-lease","velert-restore-test"],"excludedResources":["pv","pvc"],"hooks":{},"includedNamespaces":["*"],"ttl":"48h0m0s"}}}velero.io/source-cluster-k8s-gitversion=v1.21.10 velero.io/source-cluster-k8s-major-version=1 velero.io/source-cluster-k8s-minor-version=21
Phase: Failed (run
velero backup logs velero-backup-obj-a9badd03-192e-4123-8b92-ea5476d7bf84for more information)Errors: 0 Warnings: 0
Namespaces: Included: * Excluded: kube-system, kube-public, kube-node-lease, velert-restore-test
Resources: Included: * Excluded: pv, pvc Cluster-scoped: auto
Label selector:
Storage Location: default
Velero-Native Snapshot PVs: auto
TTL: 48h0m0s
Hooks:
Backup Format Version: 1.1.0
Started: 2022-05-08 14:54:13 +0000 UTC Completed: 2022-05-08 14:57:17 +0000 UTC
Expiration: 2022-05-10 14:54:13 +0000 UTC
Total items to be backed up: 1910 Items backed up: 1910
Velero-Native Snapshots:
velero 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: [Miscellaneous information that will assist in solving the issue.]
Environment:
velero version):velero client config get features):kubectl version):/etc/os-release):Vote 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.