Project

General

Profile

Actions

Bug #24568

closed

Delete marker generated by lifecycle has no owner

Added by zhang sw almost 6 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
luminous mimic
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

The delete marker generated by object expiration has no owner associated with it.


Related issues 2 (0 open2 closed)

Copied to rgw - Backport #26847: mimic: Delete marker generated by lifecycle has no ownerResolvedPrashant DActions
Copied to rgw - Backport #26848: luminous: Delete marker generated by lifecycle has no ownerResolvedPrashant DActions
Actions #2

Updated by Kefu Chai almost 6 years ago

  • Status changed from New to In Progress
  • Assignee set to zhang sw
Actions #3

Updated by Kefu Chai almost 6 years ago

  • Status changed from In Progress to Fix Under Review
Actions #4

Updated by Kefu Chai almost 6 years ago

  • Subject changed from Delete marker generated by lifecycle has no onwer. to Delete marker generated by lifecycle has no owner
Actions #5

Updated by zhang sw almost 6 years ago

According to S3, the delete marker should have owner attribute.

Actions #6

Updated by Matt Benjamin almost 6 years ago

This change seems logically correct, since delete markers may be deleted by protocol.

https://docs.aws.amazon.com/AmazonS3/latest/dev/RemDelMarker.html

I have not seen any objection thus far.

Matt

Actions #8

Updated by Casey Bodley over 5 years ago

  • Status changed from Fix Under Review to Pending Backport
  • Backport set to luminous mimic
Actions #9

Updated by Patrick Donnelly over 5 years ago

  • Copied to Backport #26847: mimic: Delete marker generated by lifecycle has no owner added
Actions #10

Updated by Patrick Donnelly over 5 years ago

  • Copied to Backport #26848: luminous: Delete marker generated by lifecycle has no owner added
Actions #11

Updated by Nathan Cutler over 5 years ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF