Skip to content
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

500 Error with S3 when uploading artifact from action #31436

Closed
neferin12 opened this issue Jun 20, 2024 · 2 comments
Closed

500 Error with S3 when uploading artifact from action #31436

neferin12 opened this issue Jun 20, 2024 · 2 comments
Labels

Comments

@neferin12
Copy link

Description

When trying to upload an artifact from an action (with actions/upload-artifact@v3) I get an 500 Error in the action.
I use s3 as storage backend.

Gitea Log:

2024-06-20T12:06:50.063046867Z 2024/06/20 12:06:50 ...actions/artifacts.go:278:uploadArtifact() [E] Error save upload chunk: save chunk to storage error: Value for x-amz-checksum-crc32c header is invalid.
2024-06-20T12:06:50.063463532Z 2024/06/20 12:06:50 ...eb/routing/logger.go:102:func1() [I] router: completed PUT /api/actions_pipeline/_apis/pipelines/workflows/20/artifacts/.../upload?itemPath=PDF%2Fmain.pdf for [fd4d:6169:6c63:6f77::e]:35712, 500 Internal Server Error in 857.2ms @ <autogenerated>:1(actions.artifactRoutes.uploadArtifact-fm)

Output of the action:

With the provided path, there will be 1 file uploaded
Starting artifact upload
For more detailed logs during the artifact upload process, enable step-debugging: https://docs.github.com/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging#enabling-step-debug-logging
Artifact name is valid!
Container for artifact "PDF" successfully created. Starting upload of file(s)
A 500 status code has been received, will attempt to retry the upload
Exponential backoff for retry #1. Waiting for 6030 milliseconds before continuing the upload at offset 0
Finished backoff for retry #1, continuing with upload
A 500 status code has been received, will attempt to retry the upload
Exponential backoff for retry #2. Waiting for 10234 milliseconds before continuing the upload at offset 0
Total file count: 1 ---- Processed file #0 (0.0%)
Finished backoff for retry #2, continuing with upload
A 500 status code has been received, will attempt to retry the upload
Exponential backoff for retry #3. Waiting for 18869 milliseconds before continuing the upload at offset 0
Total file count: 1 ---- Processed file #0 (0.0%)

Gitea Version

1.22.0

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

Docker on ubuntu 22.04 host

How are you running Gitea?

It is running on docker v26.1.3

Database

MySQL/MariaDB

@charles7668
Copy link
Contributor

What type of checksum algorithm did you use?

Maybe you can try setting the checksum algorithm to MD5.

@neferin12
Copy link
Author

Setting the checksum algorithm to MD5 solved it, thank you very much

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants