Wei-Chiu Chuang created HDDS-16622:
--------------------------------------
Summary: S3 conditional writes: If-None-Match with entity ETag
should return 412 PreconditionFailed
Key: HDDS-16622
URL: https://issues.apache.org/jira/browse/HDDS-16622
Project: Apache Ozone
Issue Type: Sub-task
Components: Ozone Manager, s3gateway
Reporter: Wei-Chiu Chuang
h2. Problem
Two ceph/s3-tests {{conditional_write}} cases reach conditional PUT/MPU logic
but fail AWS parity for {{If-None-Match}} with a concrete entity ETag on an
existing object.
h2. Expected (AWS S3 / s3-tests)
* HTTP 412 {{PreconditionFailed}} when {{If-None-Match}} matches the current
object ETag.
h2. Actual (Ozone S3 Gateway)
* HTTP 400 {{InvalidRequest}} with message that only {{If-None-Match: *}} is
supported for conditional put ({{S3ConditionalRequest.parseWriteConditions}}).
h2. Affected tests (2/7 in conditional_write)
* {{test_put_object_if_match}}
* {{test_multipart_put_object_if_match}}
h2. Evidence
* Nightly report: [Apache Ozone S3 Compatibility
Report|https://ozone.s3.peterxcli.dev/#trend-panel-section]
* Same {{conditional_write}} feature group; failures stable across nightly runs.
h2. Implementation notes (for a future fix)
* Evaluate non-wildcard {{If-None-Match}} against current ETag and return 412
when it matches; allow non-matching ETag to proceed (AWS behavior).
* Apply consistently to {{PutObject}} and {{CompleteMultipartUpload}} (both use
{{parseWriteConditions}}).
h2. Related work
Follow-up to resolved HDDS-13919 (S3 Conditional Writes PutObject) and
HDDS-15067 (Conditional CompleteMultipartUpload).
Parent: HDDS-13117
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
