Bug 1336933

Summary: rgw: multipart object corruption when uploading the same part concurrently
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Ken Dreyer (Red Hat) <kdreyer>
Component: RGWAssignee: Orit Wasserman <owasserm>
Status: CLOSED ERRATA QA Contact: ceph-qe-bugs <ceph-qe-bugs>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 1.3.2CC: cbodley, ceph-eng-bugs, ceph-qe-bugs, kbader, mbenjamin, nlevine, owasserm, smanjara, sweil, tmuthami, vumrao, yehuda
Target Milestone: rc   
Target Release: 1.3.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: ceph-0.94.5-13.el7 Ubuntu: ceph_0.94.5-7redhat1trusty Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1336931 Environment:
Last Closed: 2016-05-26 18:45:31 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:
Bug Depends On: 1336931    
Bug Blocks:    

Description Ken Dreyer (Red Hat) 2016-05-17 20:31:36 UTC 
This clone is for tracking the fix in RHCS 1.3.

+++ This bug was initially created as a clone of Bug #1336931 +++

Description of problem:

There's a certain scenario where a user can create corrupted multipart objects, by concurrent upload of the same part.


Version-Release number of selected component (if applicable):
1.3.x, 2.0

How reproducible:
always -- if done correctly


Steps to Reproduce:
1. initiate multipart upload
2. start uploading part (first upload)
3. start uploading the same part (second upload)
4. finish uploading the part (second upload)
5. finish uploading the part (first upload)
6. complete multipart upload
7. read object

Actual results:
object is corrupted

Expected results:
object should not be corrupted
Comment 7 shilpa 2016-05-26 10:58:17 UTC 
Verified on ceph-radosgw-0.94.5-13.el7cp.x86_64 using s3-test script: https://github.com/ceph/s3-tests/pull/110
Comment 8 errata-xmlrpc 2016-05-26 18:45:31 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-2016:1134