Project

General

Profile

Actions

Bug #52976

closed

'radosgw-admin bi purge' unable to delete index if bucket entrypoint doesn't exist

Added by Casey Bodley over 2 years ago. Updated 6 months ago.

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

100%

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

Description

when given both --bucket and --bucket-id, the command should be able to delete the given bucket instance/index even if the bucket entrypoint doesn't exist

steps to reproduce:

1. create a test bucket

$ s3cmd mb s3://testbucket

2. delete the bucket's entrypoint metadata

$ bin/radosgw-admin metadata rm bucket.testbucket

3. try to purge the index

$ bin/radosgw-admin bi purge --bucket testbucket --bucket-id 87129494-eac1-4a3e-860d-e9a1715aaad6.4137.1
ERROR: could not init bucket: (2) No such file or directory

--debug-ms=1 shows this osd op reply:

osd_op_reply(40 .bucket.meta.testbucket:testbucket:87129494-eac1-4a3e-860d-e9a1715aaad6.4137.1 [call,getxattrs,stat] v0'0 uv0 ondisk = -2 ((2) No such file or directory))

note that the 'testbucket:' piece is duplicated in the object name

after fixing this duplicated bucket name, the command still fails later looking for the bucket entrypoint:

osd_op_reply(42 testbucket [call,getxattrs,stat] v0'0 uv0 ondisk = -2 ((2) No such file or directory))


Related issues 2 (0 open2 closed)

Copied to rgw - Backport #53151: octopus: 'radosgw-admin bi purge' unable to delete index if bucket entrypoint doesn't existRejectedActions
Copied to rgw - Backport #53152: pacific: 'radosgw-admin bi purge' unable to delete index if bucket entrypoint doesn't existResolvedKonstantin ShalyginActions
Actions

Also available in: Atom PDF