Files
seaweedfs/test/s3/tigris_compat/expected_failures.txt
T
Chris LuandClaude Opus 5.5 b1c315b837 s3api: report no ownership controls after DeleteBucketOwnershipControls (#12748)
* test/s3: run tigrisdata-community s3-api-compat-tests in CI

Runs the suite, pinned to a commit, against weed mini through a small
provider patch, and fails on any test that is not in
expected_failures.txt or on a listed test that starts passing.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011UpvafvK8JpagF94MHWqwK

* s3api: report no ownership controls after DeleteBucketOwnershipControls

GetBucketOwnershipControls reports BucketOwnerEnforced for a bucket that
never stored a setting, so it kept reporting it after the setting was
deleted. The delete now records that it happened, and GET answers
OwnershipControlsNotFoundError until ownership is put again. How
objects are written after the delete is unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011UpvafvK8JpagF94MHWqwK

* s3api: answer DeleteBucketOwnershipControls with 204 No Content

AWS answers a successful DeleteBucketOwnershipControls with 204 and no
body; this answered 200 with an empty OwnershipControls document.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 14:25:15 -08:00

23 lines
982 B
Plaintext

# Tests from s3-api-compat-tests that SeaweedFS is expected to fail.
# check_results.py fails CI on any other failure, and on any test listed here
# that passes, so remove an entry together with the fix that makes it pass.
# AWS answers GetBucketPolicyStatus on a bucket without a policy with
# NoSuchBucketPolicy, and so does SeaweedFS; the suite expects a status.
GetBucketPolicyStatus
# Glacier restore: SeaweedFS has no archive storage class to restore from, and
# AWS also refuses RestoreObject on a STANDARD object (InvalidObjectState).
RestoreObject
# SeaweedFS reads x-amz-rename-source as a literal key first and then, when it
# starts with the request's bucket, as bucket/key, because AWS documents both
# spellings. A leading slash is dropped since filer paths cannot hold it.
RenameObject_SourceIsLiteralKey
# Not yet fixed in SeaweedFS.
PutBucketAccelerateConfiguration
GetBucketAccelerateConfiguration
PutBucketNotificationConfiguration
PutObjectTagging_VersionId