Project

General

Profile

Bug #42575

rgw: cannot cancel reshard log entry for bucket that no longer exists

Added by Eric Ivancich 11 months ago. Updated 7 months ago.

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

0%

Source:
Tags:
Backport:
nautilus,mimic
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature:

Description

It's possible to schedule a bucket for resharding via `radosgw-admin reshard add ...` and then remove the bucket. At that point resharding cannot occur and the bucket cannot be removed from the reshard log.

Allow removal from the reshard log of a non-existent bucket if --yes-i-really-mean-it is given on the command line.


Related issues

Copied to rgw - Backport #42734: mimic: rgw: cannot cancel reshard log entry for bucket that no longer exists Resolved
Copied to rgw - Backport #42735: nautilus: rgw: cannot cancel reshard log entry for bucket that no longer exists Resolved

History

#1 Updated by Eric Ivancich 11 months ago

  • Pull request ID set to 31271

#2 Updated by Casey Bodley 11 months ago

  • Status changed from Fix Under Review to 7

#3 Updated by Eric Ivancich 11 months ago

  • Status changed from 7 to Pending Backport

#4 Updated by Nathan Cutler 11 months ago

  • Copied to Backport #42734: mimic: rgw: cannot cancel reshard log entry for bucket that no longer exists added

#5 Updated by Nathan Cutler 11 months ago

  • Copied to Backport #42735: nautilus: rgw: cannot cancel reshard log entry for bucket that no longer exists added

#6 Updated by Nathan Cutler 7 months 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".

Also available in: Atom PDF