Bug 1359267

Summary: multisite: 400 error with certain complete multipart upload requests
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Orit Wasserman <owasserm>
Component: RGWAssignee: Matt Benjamin (redhat) <mbenjamin>
Status: CLOSED ERRATA QA Contact: rakesh-gm <rgowdege>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 2.0CC: cbodley, ceph-eng-bugs, hnallurv, kbader, mbenjamin, owasserm, sweil, tmuthami, tserlin, yehuda
Target Milestone: rc   
Target Release: 2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: ceph-10.2.2-27.el7cp Ubuntu: ceph_10.2.2-21redhat1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-23 19:44:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Orit Wasserman 2016-07-22 16:07:57 UTC 
Description of problem:
400 error when trying to access complete multipart upload object

Version-Release number of selected component (if applicable):


How reproducible:
Upload an object in one zone, try to access it on another

Steps to Reproduce:
1. configure multisite environment 
2. create a bucket
3. upload a multipart object in one zone
4. access the object from another zone

Actual results:
400 error

Expected results:
200 OK

Additional info:
Comment 2 Orit Wasserman 2016-07-22 16:08:42 UTC 
upstream fix: https://github.com/ceph/ceph/pull/10397
Comment 3 Yehuda Sadeh 2016-07-22 16:59:44 UTC 
The issue is not when accessing a complete object, but can happen when trying to complete a multipart upload.
Comment 4 Orit Wasserman 2016-07-22 17:05:33 UTC 
(In reply to Yehuda Sadeh from comment #3)
> The issue is not when accessing a complete object, but can happen when
> trying to complete a multipart upload.

correct.
Comment 8 errata-xmlrpc 2016-08-23 19:44:59 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://rhn.redhat.com/errata/RHBA-2016-1755.html