Open M-A-X-I-M opened 1 month ago
i have triggered a manul backup and got this as failed reason:
status: expiration: '2024-06-20T10:32:36Z' failureReason: >- rpc error: code = Unknown desc = error putting object backups/velero-manual-backup/velero-manual-backup.tar.gz: upload multipart failed, upload id: 0000018F9ABA098949D0105FA03DB64A, cause: operation error S3: UploadPart, https response error StatusCode: 400, RequestID: 0000018F9ABA09D449CAD4C0D18AF90D, HostID: 32AAAQAAEAABAAAQAAEAABAAAQAAEAABCTV75akIR2oKeSSm1d6sVCh1j7MPruom, api error XAmzContentSHA256Mismatch: The provided 'x-amz-content-sha256' header does not match what was computed.
when i downgrade the plugin-for-aws image to version v1.9.0 the backups are working
We updated: velero.image.tag: v1.13.0 -> v1.13.1 velero-plugin-for-aws: v1.9.0 -> v1.9.1 I updated helm chart: 6.3.0 -> 6.4.0
What did you expect to happen: Complete a shedule backup at night or complete a manual triggered backup, but the backups are stuck in status "finalizing"!
log of the pod:
Environment: k8s