Bug 1875305

Summary: [RGW] lifecycle ignores NoncurrentDays in NoncurrentVersionExpiration
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Harald Klein <hklein>
Component: RGWAssignee: Matt Benjamin (redhat) <mbenjamin>
Status: CLOSED ERRATA QA Contact: Tejas <tchandra>
Severity: urgent Docs Contact: Aron Gunn <agunn>
Priority: high    
Version: 4.1CC: agunn, assingh, cbodley, ceph-eng-bugs, gsitlani, kbader, kdreyer, lithomas, mbenjamin, mhackett, mmuench, pdhange, sweil, tpetr, tserlin, vereddy, vimishra, vumrao, ykaul
Target Milestone: z2Keywords: Regression
Target Release: 4.1Flags: vimishra: automate_bug+
agunn: needinfo+
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: ceph-14.2.8-107.el8cp, ceph-14.2.8-107.el7cp Doc Type: Bug Fix
Doc Text:
.Life-cycle processing ignores `NoncurrentDays` in `NoncurrentVersionExpiration` A variable which is suppose to contain the modification time of objects during parallel life-cycle processing was incorrectly initialized. This caused non-current versions of objects in buckets with a non-current expiration rule to expire before their intended expiration time. With this release, the modificaction time (`mtime`) is correctly initialized and propagates to the life-cycle's processing queue. This results in the non-current expiration to happen after the correct time period.
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-30 17:26:56 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:
Bug Depends On:    
Bug Blocks: 1816167    

Comment 27 errata-xmlrpc 2020-09-30 17:26:56 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Red Hat Ceph Storage 4.1 Bug Fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4144