busyboy77
commented
1 month ago Update:
I also tried with
kubectl patch deployment velero -n velero --patch \
'{"spec":{"template":{"spec":{"containers":[{"name": "velero", "resources": {"limits":{"cpu": "1", "memory": "2Gi"}, "requests": {"cpu": "1", "memory": "2Gi"}}}]}}}}'to make sure if this due to resources constraints but still the problem persists.
blackpiglet
What steps did you take and what happened: with Velero 1.14.0
I'm running a VM on Contabo with RKE2 running v1.27.12+rke2r1 version of K8s. and I'm trying to push the velero based backups to DigitalOcean's S3 Object Storage.
tied to Digitalocean's S3 Object storage using below given command
my backup-location status
list of velero plugins
so far logs kubectl logs deploy velero .txt
tried to take backup of the mongodb pod ( deployed using helm chart
Annotated the pod using
Created backup for mongo using
So far logs -- still in progress
velero-backup-describe-ef-mongo--details.txt
backup is uploading untill it reaches 2.37 Gb
after 2 minutes
Now the Failure part
backup is failed with
with logs as per kubectl-logs-deployment-velero-n-velero.txt
It always fails the backup exactly at 2.37 Gb with 131 items
Just to note:
1.,the same backup works with minio deployment without any errors
What did you expect to happen:
The backup fails after a certain period of time
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 --helpAttached as bundle-2024-07-23-16-48-25.tar.gzIf 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 veleroAttachedvelero backup describe <backupname>orkubectl get backup/<backupname> -n velero -o yamlPhase: Failed (run
velero backup logs ef-mongofor more information)Namespaces: Included: ef-external Excluded:
Resources: Included: pods, persistentvolumeclaims, persistentvolumes Excluded:
Cluster-scoped: auto
Label selector: app.kubernetes.io/name=mongodb
Or label selector:
Storage Location: default
Velero-Native Snapshot PVs: auto Snapshot Move Data: false Data Mover: velero
TTL: 720h0m0s
CSISnapshotTimeout: 10m0s ItemOperationTimeout: 4h0m0s
Hooks:
Backup Format Version: 1.1.0
Started: 2024-07-23 16:37:06 +0200 CEST Completed: <n/a>
Expiration: 2024-08-22 16:37:06 +0200 CEST
Total items to be backed up: 3 Items backed up: 3
Backup Volumes: Velero-Native Snapshots:
CSI Snapshots:
Pod Volume Backups - kopia (specify --details for more information): Completed: 1
HooksAttempted: 0 HooksFailed: 0
velero backup logs ef-mongo An error occurred: file not found
velero client config get features
features:
v1.27.12+rke2r1
WMWare VM
/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.