Bug #6056
closedrgw: sync agent is not propagating bucket delete
0%
Description
A new test that deletes an existing bucket on the source, then does a sync, then tries to get info for that bucket on the source and destination is finding info for the bucket on the destination but not the source.
I pushed teuthology branch 'wip-buck-5605' with example test code that will display this behavior. Just run the radosgw-admin task with an RGW congfigured with zones. I'll attach an example YAML file to the ticket.
I'm also attaching the output from a teuthology run. There's an error showing up that may just be noise or may be related. It looks like the agent is unable to get or set worker bounds due to not being able to access the rados log pool (but I don't know why it's not able to). Example below:
DEBUG:requests.packages.urllib3.connectionpool:"POST /admin/log?lock&locker-id=mira03730462&length=60&zone-id=r0z1&type=metadata&id=60 HTTP/1.1" 200 None
DEBUG:boto:path=//admin/replica_log?bounds
DEBUG:boto:auth_path=//admin/replica_log?bounds
DEBUG:boto:StringToSign:
GET
Mon, 19 Aug 2013 02:11:11 GMT
/admin/replica_log
INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): mira053.front.sepia.ceph.com
DEBUG:requests.packages.urllib3.connectionpool:"GET /admin/replica_log?bounds&type=metadata&id=60 HTTP/1.1" 404 20
INFO:teuthology.task.rgw.client.1.out:[10.214.133.106]: 2013-08-18 19:11:11.612117 7ff8f97b2700 -1 ERROR: could not open rados pool .region1.r1z1.log_pool
Files
Updated by Anonymous over 10 years ago
I should have noted that I would expect that info for the bucket should not be found on either the source or the destination.
Updated by Yehuda Sadeh over 10 years ago
- Status changed from New to Fix Under Review
We end up not removing the bucket entry point, although the bucket is unlinked from the user.
Updated by Ian Colle over 10 years ago
- Assignee changed from Josh Durgin to Greg Farnum
Tag, Greg, you're it.
Updated by Greg Farnum over 10 years ago
- Status changed from Fix Under Review to In Progress
- Assignee changed from Greg Farnum to Yehuda Sadeh
You've got my Reviewed-by: with the comment change we discussed, assuming you've tested it.
Updated by Yehuda Sadeh over 10 years ago
- Status changed from In Progress to Resolved
Fixed, commit:2632846e24e3c26139e982e0a569951d25e1589b