-
Notifications
You must be signed in to change notification settings - Fork 647
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multipart upload to AWS S3 fails in Argo Workflows #1776
Comments
might be similar issue? https://gitlab.gnome.org/Infrastructure/GitLab/-/issues/612 |
Seems like turning off encryption options resolved the issue while preserving SSE-S3 type of encryption for all uploads (there is no option to turn the encryption off completely in S3 anymore). This can be a hiccup on AWS side or they started validating against double encryption (for lack of a better term). |
This is because of a header set during CompleteMultipartUpload() call @nazarewk |
Continuing #1025 , I seem to have the same issue.
I have
SSE-S3
configured Artifacts bucket and for files above 5MB I'm getting the same error as #1025 :failed to put file: x-amz-server-side-encryption header is not supported for this operation.
The call seems to originate here in Argo Workflows (not doing anything funny): https://github.com/argoproj/argo-workflows/blob/2f5e7534c44499a9efce51d12ff87f8c3f725a21/workflow/artifacts/s3/s3.go#L202-L204
The text was updated successfully, but these errors were encountered: