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 Additional info:
We will take this change in as part of the rebase to ceph 10.2.2.
Ran the automated suite from here https://github.com/ceph/s3-tests the test related to this is : https://github.com/ceph/s3-tests/blob/master/s3tests/functional/test_s3.py#L5907 the test passed and hence marking this test case as verified.
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