Actions
Bug #42575
closedrgw: cannot cancel reshard log entry for bucket that no longer exists
% Done:
0%
Source:
Tags:
Backport:
nautilus,mimic
Regression:
No
Severity:
3 - minor
Reviewed:
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.
Updated by Casey Bodley over 4 years ago
- Status changed from Fix Under Review to 7
Updated by J. Eric Ivancich over 4 years ago
- Status changed from 7 to Pending Backport
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #42734: mimic: rgw: cannot cancel reshard log entry for bucket that no longer exists added
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #42735: nautilus: rgw: cannot cancel reshard log entry for bucket that no longer exists added
Updated by Nathan Cutler about 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