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

ASF GitHub Bot updated HDDS-16005:
----------------------------------
    Labels: pull-request-available  (was: )

> DeleteBucketLifecycle should return 204 No Content when no lifecycle policy 
> exists
> ----------------------------------------------------------------------------------
>
>                 Key: HDDS-16005
>                 URL: https://issues.apache.org/jira/browse/HDDS-16005
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Chung-En Lee
>            Assignee: Nicolas Lu
>            Priority: Major
>              Labels: pull-request-available
>
> According to Amazon S3 API specification, DeleteBucketLifecycle (DELETE 
> Bucket lifecycle) should be idempotent and return 204 No Content even if no 
> lifecycle configuration exists on the bucket.
> Currently, Ozone S3G throws NoSuchLifecycleConfiguration (404 Not Found) when 
> calling DeleteBucketLifecycle on a bucket without a lifecycle rule, causing 
> s3-tests (test_lifecycle_delete) to fail with ClientError.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to