Bug #21681: Enabling Lifecycle on a bucket, for expiration day=0, getting XML error (should parse and apply policy) - rgw - Ceph

Actions

Copy link

Bug #21681

open

Enabling Lifecycle on a bucket, for expiration day=0, getting XML error (should parse and apply policy)

Added by Matt Benjamin over 6 years ago. Updated over 4 years ago.

Status:

New

Priority:

Normal

Assignee:

Matt Benjamin

Target version:

% Done:

Source:

Tags:

Backport:

luminous

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Pull request ID:

Crash signature (v1):

Crash signature (v2):

Description

Description of problem:
Enable lifecycle on a bucket and set the number of days to 0, which expires objects immediately. It returned XML error instead of deleting objects.

Version-Release number of selected component (if applicable):
Ceph 3.0

How reproducible:
Always

Steps to Reproduce:
1.Set up a ceph 3.0 cluster.
2.Enable lifecycle on a bucket.
3.Set expiration for objects to 0 day(s).
4.Objects will get deleted immediately.

Actual results:

[root@magna118 ~]# python tc11198.py
log/0ABC.txt
Traceback (most recent call last):
File "tc11198.py", line 38, in <module>
mybucket.configure_lifecycle(lifecycle)
File "/usr/lib/python2.7/site-packages/boto-2.48.0-py2.7.egg/boto/s3/bucket.py", line 1366, in configure_lifecycle
response.status, response.reason, body)
boto.exception.S3ResponseError: S3ResponseError: 400 Bad Request
<Error><Code>InvalidArgument</Code><BucketName>redhat</BucketName><RequestId>tx0000000000000000001f7-0059bb820b-1077-default</RequestId><HostId>1077-default-default</HostId></Error>

Expected results:
Should parse and store policy.

(Originally reported by downstream, Shreekara Shreekanthshastri Shivarajpura)