Description of problem: Some S3 clients utilize "/" in their upload IDs. RadosGW cannot handle this properly and returns a 403. Version-Release number of selected component (if applicable): v0.80.7 (firefly) How reproducible: Easily reproducible. Steps to Reproduce: 1. Utilize a client that includes a "/" in the upload ID for multipart uploads (confirmed: TNTDrive or Updraft Plus or AWS SDK JS v.2.0.29) 2. Receive 403 from RadosGW Actual results: RadosGW cannot properly decode "/" and returns a 403 Expected results: RadosGW should properly decode "/" in the upload ID and continue Additional info: Regression introduced in a fix for this bug: http://tracker.ceph.com/issues/8702
Note that it's not that radosgw cannot decode the slash properly, it's the client fails to sign the request correctly having the slash there. The workaround is not to use slashes for that as the client doesn't handle it correctly. The upstream bug for this issue is #10271, and a fix has already been pushed upstream (master, giant, firefly).
Yehuda, is this fix in 0.80.8?
(In reply to Neil Levine from comment #2) > Yehuda, is this fix in 0.80.8? No, it didn't make the cutoff. It will be in the following version.
I don't see a firefly-specific PR upstream so I guess the patches were pushed directly to the firefly branch. https://github.com/ceph/ceph/commit/24c13d87039d4f61df0bcabdb8862e0e94fe575d https://github.com/ceph/ceph/commit/617002d3ff469ef409a83e35d4f4fd6a0b5b1278 These are present in upstream's v0.80.9.
*** Bug 1233529 has been marked as a duplicate of this bug. ***
*** Bug 1233530 has been marked as a duplicate of this bug. ***
Presuming this already fixed in Hammer/1.3.0 — if not, please dupe bug and NEEDINFO me for ack.
(In reply to Federico Lucifredi from comment #9) > Presuming this already fixed in Hammer/1.3.0 — if not, please dupe bug and > NEEDINFO me for ack. Correct, the necessary commits are already in v0.94.1 upstream (and RHCS 1.3.0), as 5fc7a0be67a03ed63fcc8408f8d71a31a1841076 and 21e07eb6abacb085f81b65acd706b46af29ffc03 .
Works on 1.2.3.2 iso's for trusty and precise.
Works on 1.2.3.2 iso's for Centos 6.7
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-2015-1703.html