Bug #52976
closed'radosgw-admin bi purge' unable to delete index if bucket entrypoint doesn't exist
100%
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))
Updated by Casey Bodley over 2 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 43591
Updated by Casey Bodley over 2 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot over 2 years ago
- Copied to Backport #53151: octopus: 'radosgw-admin bi purge' unable to delete index if bucket entrypoint doesn't exist added
Updated by Backport Bot over 2 years ago
- Copied to Backport #53152: pacific: 'radosgw-admin bi purge' unable to delete index if bucket entrypoint doesn't exist added
Updated by Backport Bot over 1 year ago
- Tags changed from admin to admin backport_processed
Updated by Konstantin Shalygin 5 months ago
- Status changed from Pending Backport to Resolved
- % Done changed from 0 to 100