Bug 1700336 - RW Bucket Lifecycle configuration modification is not getting updated after setting unless the existing policy is deleted and set again
Summary: RW Bucket Lifecycle configuration modification is not getting updated after s...
Keywords:
Status: CLOSED DUPLICATE of bug 1708650
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW
Version: 3.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 3.3
Assignee: Matt Benjamin (redhat)
QA Contact: ceph-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-16 10:42 UTC by rakesh-gm
Modified: 2019-05-10 14:41 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-10 14:41:11 UTC
Embargoed:


Attachments (Terms of Use)

Description rakesh-gm 2019-04-16 10:42:30 UTC
Created attachment 1555462 [details]
lc.py

Objects in RGW bucket expires even after setting status as disabled in  lifecycle configuration  

Adding "rgw lc debug interval = 300" for testing purposes (5 mins)
(this will set expiration to 5 mins if expiration days is set to 1 day)

Ceph Version: ceph version 12.2.8-116.el7cp 
OS: RHEL 7.6

Steps: 

using boto3

1. create a bucket, 
2. upload object
3. put bucket lifecycle configuration, using expiration day as "1" and add status as "Enabled",  
4. now set the disable the configuration by setting status as "Disabled", the response says 200 ok.
5. now get the bucket life cycle configuration and check for the status, it shows "Enabled"
6. check if the object is expired after 5 mins -- the object does not exist

Expected: 
After disabling the lifecycle configuration, the object should not get deleted

I have used the attached script to set the lifecycle, for enabling and disabling.

Comment 9 Matt Benjamin (redhat) 2019-05-10 14:41:11 UTC

*** This bug has been marked as a duplicate of bug 1708650 ***


Note You need to log in before you can comment on or make changes to this bug.