Actions
Bug #265
closedRemoving a bucket doesn't clean up object in .rgw pool
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
When removing a bucket, the corresponding object in the .rgw pool doesn't get removed, thus preventing us from creating the same bucket again:
Before removing the bucket beta
root@node14:~# rados lspools 10.07.08_10:42:46.369198 7f38d538a710 monclient(hunting): found mon0 data metadata casdata rbd .rgw .users wido alpha beta root@node14:~# rados ls -p .rgw 10.07.08_10:42:51.268858 7f7864d65710 monclient(hunting): found mon1 .users alpha beta wido root@node14:~#
Then we try to remove it:
wido@wido-desktop:~$ s3 -u delete beta wido@wido-desktop:~$
Seems to go fine, the rados pool is removed, but not the beta object in the .rgw pool:
root@node14:~# rados lspools 10.07.08_10:45:36.129251 7f7f4f301710 monclient(hunting): found mon0 data metadata casdata rbd .rgw .users wido alpha root@node14:~# rados ls -p .rgw 10.07.08_10:45:37.259169 7f51a3782710 monclient(hunting): found mon0 .users alpha beta wido root@node14:~#
Manually removing the beta object lets us re-create the bucket:
root@node14:~# rados rm beta -p .rgw 10.07.08_10:46:08.398889 7f7aff8a5710 monclient(hunting): found mon1 root@node14:~#
Updated by Greg Farnum almost 14 years ago
- Status changed from New to Closed
- Assignee set to Greg Farnum
Fixed in commit af65f15b855819188aae9952d38a2cc035265417
Updated by Sage Weil about 13 years ago
- Project changed from 4 to Ceph
- Category changed from radosgw to 22
Updated by John Spray over 6 years ago
- Project changed from Ceph to rgw
- Category deleted (
22)
Bulk reassign of radosgw category to RGW project.
Actions