Actions
Bug #70614
closedinvalid checksum should return BadDigest
% Done:
0%
Source:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Tags (freeform):
Merge Commit:
Fixed In:
v20.0.0-894-gf9a8403ca9
Released In:
v20.2.0~716
Upkeep Timestamp:
2025-11-01T01:13:57+00:00
Description
When uploading an S3 object with an invalid checksum, the return code should be BadDigest to mirror more closely the AWS S3 implementation. See: https://docs.aws.amazon.com/AmazonS3/latest/userguide/checking-object-integrity.html
Currently, the behavior varies for different algorithms:
For MD5, return code is InvalidDigest
For others like SHA1/256, return code is InvalidRequest
Updated by Matt Benjamin 11 months ago ยท Edited
hi alex,
I can address this in the new checksums PR: https://github.com/ceph/ceph/pull/61878
Matt
Updated by Alex Wojno 11 months ago
- Assignee changed from Alex Wojno to Matt Benjamin
Great, thanks @Matt Benjamin. Assigning over to you.
Updated by Matt Benjamin 11 months ago
- Status changed from New to Fix Under Review
- Pull request ID set to 61878
Updated by Casey Bodley 11 months ago
- Status changed from Fix Under Review to Resolved
Updated by Upkeep Bot 8 months ago
- Merge Commit set to f9a8403ca94275522eac100316a68de12165f58e
- Fixed In set to v20.0.0-894-gf9a8403ca94
- Upkeep Timestamp set to 2025-07-09T19:08:09+00:00
Updated by Upkeep Bot 7 months ago
- Fixed In changed from v20.0.0-894-gf9a8403ca94 to v20.0.0-894-gf9a8403ca9
- Upkeep Timestamp changed from 2025-07-09T19:08:09+00:00 to 2025-07-14T18:12:52+00:00
Updated by Upkeep Bot 4 months ago
- Released In set to v20.2.0~716
- Upkeep Timestamp changed from 2025-07-14T18:12:52+00:00 to 2025-11-01T01:13:57+00:00
Actions