Closed leandreArturia closed 3 months ago
@leandreArturia May I know which version of Minio are you using? I believe the change in aws-plugin v1.9.1 has been verified against Minio cc @danfengliu
Additionally, please check aws-plugin v1.9.2 for the workaround to skip adding checksum header, you will need to make a change to the BSL.
@leandreArturia May I know which version of Minio are you using? I believe the change in aws-plugin v1.9.1 has been verified against Minio cc @danfengliu
Additionally, please check aws-plugin v1.9.2 for the workaround to skip adding checksum header, you will need to make a change to the BSL.
I have a pretty old minio : minio version RELEASE.2022-08-25T07-17-05Z
I will check for the 1.9.2 aws plugin.
EDIT: It works with the aws plugin 1.9.2, thank you @reasonerjt
@leandreArturia Thank you for the update, let me keep this open until we double checked in our pipeline.
In Velero nightly pipeline, Minio version is 2024-04-18T19-09-19Z without CA, and pipeline passed, no such error occurred.
containerStatuses:
- containerID: containerd://edabecc8a9bede9288bfc293af7a408e115989ed1d6437098787df4cc96565a1
image: docker.io/minio/minio:RELEASE.2024-04-18T19-09-19Z
imageID: docker.io/minio/minio@sha256:036a068d7d6b69400da6bc07a480bee1e241ef3c341c41d988ed11f520f85124
lastState: {}
name: minio
ready: true
restartCount: 0
started: true
state:
running:
Either options work - went with 2
checksumAlgorithm: ""
to skip checks on Minio
---
apiVersion: velero.io/v1
kind: BackupStorageLocation
metadata:
name: example
spec:
config:
region: minio
s3ForcePathStyle: "true"
s3Url: https://example.com
# Disable checksumAlgorithm to avoid issues with Minio
# https://github.com/vmware-tanzu/velero-plugin-for-aws/pull/197
checksumAlgorithm: ""
default: true
objectStorage:
bucket: example
provider: aws
credential:
name: cloud-credentials
key: cloud
I'm using a TrueNAS Minio service, on Velero 1.13.2
.
Thanks for the fix!
I think we can close this if you don't mind. @johnnyhuy has summarized the 2 solutions.
Same problem but with Linode Object storage, solution to empty the checksumAlgorithm works.
@jaredkipe having the same issue with linode, but with aws v1.9.0, so no checksumAlgorithm field and still getting errors. can you please share your BackupStorageLocation configs?
Also having the same issue with Linode and disabled checksumAlgorithm
What steps did you take and what happened:
Installed Velero 1.13.0 with CSI snapshot via Helm (
vmware-tanzu/velero --version 6.0.0
) . Here is my configuration :I have a minIO deployed with self-signed certificate.
I was previously on velero 1.6 (with restic) without volumeSnapshot and the backup worked (with the same S3 credentials)
Now, when I try to do a backup, the volumeSnapshot work well but the backup fail:
What did you expect to happen:
To get a backup.
The following information will help us better understand what's going on:
bundle-2024-04-17-12-10-16.tar.gz
Environment:
velero version
): Server 1.13.0 Client 1.9.1velero client config get features
): Nonekubectl version
):Server Version: v1.26.9+rke2r1
/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.