Describe the bug

Due to recent changes in the AWS SDK alternative implementations of the S3 API are no longer working with vmbackup 1.112.0 or later since they do not implement checksuming. So far we know that ceph and linode's S3 implementations are affected.

To Reproduce

1. run vmbackup with an s3 url pointed to ceph or linode
2. receive the following output

cannot create backup: cannot upload part{path: "indexdb/182C61247B4E051A/parts.json", file_size: 590, offset: 0, size: 590} to S3{bucket: "backup-bucket-123", dir: "vmstorage-0/latest/"}: cannot upload data to "indexdb/182C61247B4E051A/parts.json" at S3{bucket: "backup-bucket-123", dir: "vmstorage-0/latest/"} (remote path "vmstorage-0/latest/indexdb/182C61247B4E051A/parts.json/000000000000024E_0000000000000000_000000000000024E"): operation error S3: PutObject, https response error StatusCode: 400, RequestID: tx000004f2728d16b3658d8-0067d81d11-abadb1fa-default, HostID: abadb1fa-default-default, api error XAmzContentSHA256Mismatch: UnknownError

Version

vmbackup 1.112.0 or later

Logs

No response

Screenshots

No response

Used command-line flags

No response

Additional information

To work around this issue the version of vmbackup should be downgraded to v1.111. For a more permanent fix the version of the AWS SDK should be pinned to version prior to the checksumming change being added.