Cannot backup on s3_compatible with version 0.24.1 (XAmzContentSHA256Mismatch) #873
Description
I can't backup any node using an s3_compatible storage with the latest medusa version 0.24.1.
Downgrading to 0.24.0 fixes the issue
Upon backup, this is the error I receive in my console:
[2025-06-24 11:12:50,559] ERROR: An error occurred (XAmzContentSHA256Mismatch) when calling the PutObject operation: The Content-SHA256 you specified did not match what we received
[2025-06-24 11:13:10,670] ERROR: An error occurred (XAmzContentSHA256Mismatch) when calling the PutObject operation: The Content-SHA256 you specified did not match what we received
[2025-06-24 11:13:50,764] ERROR: An error occurred (XAmzContentSHA256Mismatch) when calling the PutObject operation: The Content-SHA256 you specified did not match what we received
This goes on and on util I hit Ctrl-C and nothing is stored on my bucket.
From a quick research, this problem seems to be related to the version of the boto library which was bumped to a more recent version in the latest release.
I found an issue on the apache-iceberg project which looks exactly like the problem I'm facing: apache/iceberg-python#1546. There's also an open PR related to the issue implementing a legacy MD5 checksum plugin for endpoints who need it: apache/iceberg#12264
I didn't get time to dig into medusa code and see if I can implement this plugin of disable checksum validation to test further.
Since I saw an other issue on s3fs project (fsspec/s3fs#855) stating this could be related to not using ssl correctly, I made sure connection to my endpoint was verified correctly but this did not change anything
[2025-06-24 11:12:49,846] INFO: Connecting to s3_compatible with args {'endpoint_url': 'https://s3.my.redacted.domain:443', 'verify': True}
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: MED-135