[jira] [Issue Comment Deleted] (HDDS-5523) s3_compatibility tests/Multipart upload

["George Jahad (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDDS-5523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

George Jahad updated HDDS-5523:
-------------------------------
    Comment: was deleted

(was: https://github.com/apache/ozone/pull/2509)

> s3_compatibility tests/Multipart upload
> ---------------------------------------
>
>                 Key: HDDS-5523
>                 URL: https://issues.apache.org/jira/browse/HDDS-5523
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: S3
>            Reporter: George Jahad
>            Assignee: George Jahad
>            Priority: Minor
>              Labels: pull-request-available
>
> Note this was split off from:
> https://issues.apache.org/jira/browse/HDDS-5458
>  
> "Test Multipart Upload Put With Copy and range with IfModifiedSince"
> The current s3 script fails on this test, where a file is uploaded and then tested with "IfModifiedSince".
> The original file hasn't been modified, so the upload is expected to fail. But on AWS, the upload succeeds. The problem is that the test sets the "IfModifiedSince" into the future.
> In that case AWS ignores the Precondition and does the upload even though "IfModifiedSince" is false.
> This is a known issue with how the API works on AWS: [https://forums.aws.amazon.com/thread.jspa?threadID=88985]
>  
> Currently the test sets the "IfModifiedSince" time to a full day in the future. To fix it, we could modify the test to set the "IfModifiedSince" time to be a few seconds after the creation time, and pause till that time has passed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org