Project

General

Profile

Bug #21533

rgw:lc: obj expiration time is not the same as S3

Added by shasha lu almost 2 years ago. Updated almost 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
09/25/2017
Due date:
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:

Description

Amazon S3 calculates the expiration time by adding the number of days specified in the rule to the object creation time and rounding the resulting time to the next day midnight.

For rgw, if you create a obj at 2017-09-24,01:00:00. And expiration days is 1.
If the bucket lc was scheduled at 2017-09-25,02:00:00, the obj will expiry.
If the bucket lc was scheduled at 2017-09-25,00:10:00, the obj will not expiry at 2017-09-25.

For S3, the object will expiry at 2017-09-26.

So rgw should using the rounding down midnight time to compare with the object creation time to check obj expiration.

Also available in: Atom PDF