Project

General

Profile

Actions

Bug #36763

closed

rgw: set null version object issues

Added by Tianshan Qu over 5 years ago. Updated over 4 years ago.

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

0%

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

Description

1.set null version object acl will create empty index
RGWRados::set_attrs did not clear instance, so index prepare, complete got instance=null,
which lead to empty index 1000_<obj>_i_null.
there is no harm to create empty index, but listomapkeys to find that key.

2.if object is exist with versioned key, we can set none exists null version object
order:
1) enable bucket version
2) put obj
3) disable bucket version
4) set versoned_id=null acl will succeed which should not


Related issues 3 (0 open3 closed)

Copied to rgw - Backport #40358: nautilus: rgw: set null version object issuesResolvedNathan CutlerActions
Copied to rgw - Backport #40359: luminous: rgw: set null version object issuesResolvedNathan CutlerActions
Copied to rgw - Backport #40360: mimic: rgw: set null version object issuesResolvedNathan CutlerActions
Actions #2

Updated by Casey Bodley over 5 years ago

  • Status changed from New to Fix Under Review
Actions #3

Updated by Casey Bodley almost 5 years ago

  • Status changed from Fix Under Review to Pending Backport
  • Tags set to versioning
  • Backport set to luminous mimic nautilus
Actions #4

Updated by Nathan Cutler almost 5 years ago

  • Copied to Backport #40358: nautilus: rgw: set null version object issues added
Actions #5

Updated by Nathan Cutler almost 5 years ago

  • Copied to Backport #40359: luminous: rgw: set null version object issues added
Actions #6

Updated by Nathan Cutler almost 5 years ago

  • Copied to Backport #40360: mimic: rgw: set null version object issues added
Actions #7

Updated by Nathan Cutler over 4 years ago

  • Pull request ID set to 25044
Actions #8

Updated by Nathan Cutler over 4 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Actions

Also available in: Atom PDF