Fix tool for #11442 does not correctly fix objects created via multipart uploads
radosgw-admin bucket check --check-head-obj-locator --fix claims to successfully fix objects that were created via multipart uploads, and subsequent
--check-head-obj-locator invocations claim that the objects have, in fact, been fixed. However, those objects remain inaccessible by rgw 0.94.2, and remain accessible by rgw 0.94.1.
rgw: fix reset_loc()
Only need to set locator for underscore if namespace is empty
Signed-off-by: Yehuda Sadeh <email@example.com>
(cherry picked from commit d3bd27f4855df6bb207b656527138026af1a36a2)
- Status changed from New to Duplicate
#11984 appears to be about a harmless warning produced by the tool. This bug is about the tool failing to fix the problem it was designed to fix.
do you have any example of an object that was created with multipart upload that is not accessible? Does the object name start with an underscore, or is it every multipart object?
- Status changed from Duplicate to New
In my tests, it seemed to affect all multipart objects starting with an underscore and created with 0.94.1. I've since reuploaded every affected object in our system, but I can downgrade an rgw and reproduce the problem again if that's helpful.
- Priority changed from Normal to Urgent
- Status changed from New to Pending Backport
- Backport set to hammer
merged to next, commit:0f6060c7c8e4576039a54080d17536e2169b6f63
- Assignee set to Loic Dachary
- Assignee changed from Loic Dachary to Yehuda Sadeh
- Status changed from Pending Backport to Resolved
Also available in: Atom