I am at the Ceph Day at CERN, I asked to Sage if it is supported to enable both S3 and swift API at the same time. The answer is yes, so it is meant to be supported, and this that we see here is probably a bug. I opened a bug report: http://tracker.ceph.com/issues/16293 If anyone has a chance to test it on a ceph version newer than Hammer, you can update the bug :) thank you Saverio 2016-05-12 15:49 GMT+02:00 Yehuda Sadeh-Weinraub <yehuda@xxxxxxxxxx>: > On Thu, May 12, 2016 at 12:29 AM, Saverio Proto <zioproto@xxxxxxxxx> wrote: >>> While I'm usually not fond of blaming the client application, this is >>> really the swift command line tool issue. It tries to be smart by >>> comparing the md5sum of the object's content with the object's etag, >>> and it breaks with multipart objects. Multipart objects is calculated >>> differently (md5sum of the md5sum of each part). I think the swift >>> tool has a special handling for swift large objects (which are not the >>> same as s3 multipart objects), so that's why it works in that specific >>> use case. >> >> Well but I tried also with rclone and I have the same issue. >> >> Clients I tried >> rclone (both SWIFT and S3) >> s3cmd (S3) >> python-swiftclient (SWIFT). >> >> I can reproduce the issue with different clients. >> Once a multipart object is uploaded via S3 (with rclone or s3cmd) I >> cannot read it anymore via SWIFT (either with rclone or >> pythonswift-client). >> >> Are you saying that all SWIFT clients implementations are wrong ? > > Yes. > >> >> Or should the radosgw be configured with only 1 API active ? >> >> Saverio _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |