Bug 1525334 - RGW multipart uploads fail with resharded buckets
Summary: RGW multipart uploads fail with resharded buckets
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW
Version: 2.4
Hardware: All
OS: All
unspecified
high
Target Milestone: rc
: 2.5
Assignee: Matt Benjamin (redhat)
QA Contact: Tejas
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-13 04:25 UTC by Matt Benjamin (redhat)
Modified: 2018-02-21 19:47 UTC (History)
9 users (show)

Fixed In Version: RHEL: ceph-10.2.10-9.el7cp Ubuntu: ceph_10.2.10-6redhat1xenial
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2018-02-21 19:47:28 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 22368 0 None None None 2017-12-13 04:25:12 UTC
Red Hat Product Errata RHBA-2018:0340 0 normal SHIPPED_LIVE Red Hat Ceph Storage 2.5 bug fix and enhancement update 2018-02-22 00:50:32 UTC

Description Matt Benjamin (redhat) 2017-12-13 04:25:13 UTC 
Description of problem:
After resharding, old bucket id used in complete multipart.
Comment 3 Ken Dreyer (Red Hat) 2017-12-21 21:25:43 UTC 
Matt, this does not affect RHCEPH 3.0 right?
Comment 5 Matt Benjamin (redhat) 2017-12-21 21:37:33 UTC 
(In reply to Ken Dreyer (Red Hat) from comment #3)
> Matt, this does not affect RHCEPH 3.0 right?

right
Comment 11 Tejas 2018-01-12 09:01:38 UTC 
Verified in build:
ceph version 10.2.10-8.el7cp

After reshard we are able to Upload objects the same way as prior to reshard.
Comment 14 errata-xmlrpc 2018-02-21 19:47:28 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0340
Note You need to log in before you can comment on or make changes to this bug.