Bug 1700336

Summary: RW Bucket Lifecycle configuration modification is not getting updated after setting unless the existing policy is deleted and set again
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: rakesh-gm <rgowdege>
Component: RGWAssignee: Matt Benjamin (redhat) <mbenjamin>
Status: CLOSED DUPLICATE QA Contact: ceph-qe-bugs <ceph-qe-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.2CC: assingh, cbodley, ceph-eng-bugs, kbader, mbenjamin, sweil, tchandra, tserlin
Target Milestone: rc   
Target Release: 3.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-10 14:41:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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 ***