Project

General

Profile

Feature #5219

"radosgw-admin user check" should handle non-existent buckets in index

Added by Greg Farnum about 6 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
05/31/2013
Due date:
% Done:

0%

Source:
Support
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

Right now, if "radosgw-admin user check" encounters a bucket whose object doesn't exist it uses default values (because RGWRados::get_bucket_info() lies), and so the index gets set to those instead of removing the item. If that function behavior changes (it will change with the DR/geo work we're putting in, and I may backport it as well), then user check just skips the bucket and doesn't try to fix it at all.

Instead, we probably want it to remove the user index's omap entry.

Also available in: Atom PDF