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

[upload] Error with Protocol S3 on Fedora41 #3921

Open
TrevorBenson opened this issue Feb 7, 2025 · 3 comments
Open

[upload] Error with Protocol S3 on Fedora41 #3921

TrevorBenson opened this issue Feb 7, 2025 · 3 comments

Comments

@TrevorBenson
Copy link
Member

TrevorBenson commented Feb 7, 2025

Using a non Amazon AWS S3 endpoint with upload protocol s3 results in error:

Upload attempt failed: Failed to upload to S3: Failed to upload /var/tmp/sosreport-fedora-2025-02-07-edtislu.tar.xz to sreport/XXXXXXXX/2025/01/sosreport-fedora-2025-02-07-edtislu.tar.xz: An error occurred (BadRequest) when calling the PutObject operation: trailing checksum is not supported

This was on Fedora 41. I went ahead and tested against Enterprise distros, instead of community workstation/desktops, as that is the primary platforms for my s3 upload use case. I confirmed that both EL8 with sos-4.7.2 and python3-boto3-1.15.15 and EL9 with sos-4.8.1 and python3-boto3-1.28.62 this error is not observed when running sos report --upload.

Due to the above tests working I figured it was specific to fedora and no ongoing work in sos which was also being tested. I found the same issue regardless of sos-4.8.2-1 and sos-4.8.0-1. I did however isolate it to when using python3-boto3-1.36.12-1.fc41. When I downgraded to python3-boto3-1.35.37-1.fc41 the error goes away and the s3 uploads to non AWS S3 endpoints once again work.

@pmoravec
Copy link
Contributor

pmoravec commented Feb 7, 2025

Maybe the problem is in the python3-boto3 library, then? If older version of the library works well..? (or do we use the library in some wrong way..?)

@TrevorBenson
Copy link
Member Author

TrevorBenson commented Feb 7, 2025

Maybe the problem is in the python3-boto3 library, then? If older version of the library works well..? (or do we use the library in some wrong way..?)

At the moment I'm not sure if boto3 has a bug, or simply made a change which was not backwards compatible.

I'll look into it more deeply and if it's a bug open an issue with that repository, if not I'll submit a fix here to address the change in method usage.

@TrevorBenson
Copy link
Member Author

I suspect it's rooted in this current issue:
boto/boto3#4409

Yesterday I recall this error when testing non AWS buckets. Today I limited the report plugins to only the block plugin to speed up testing, which made the archive smaller than the default size for splitting MPU's, changing the error.

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

No branches or pull requests

2 participants