Ok, but why this happend. There is no new code started before this problem. Is there any way to recover cluster to normal operation withoud Access Denied in s3 any acl operation ?? On Tue, Sep 11, 2012 at 11:32 PM, Yehuda Sadeh <yehuda@xxxxxxxxxxx> wrote: > On Tue, Sep 11, 2012 at 2:28 PM, Sławomir Skowron <szibis@xxxxxxxxx> wrote: >> :~# s3 -u put ocdn/test3 cannedAcl=public-read < /tmp/testdl >> :~# s3 -u get ocdn/test3 > /tmp/test3 >> :~# HEAD http://127.0.0.1/ocdn/test3 >> 200 OK >> Connection: close >> Date: Tue, 11 Sep 2012 21:23:19 GMT >> Accept-Ranges: bytes >> ETag: "a241f32b8cf07f90d36b5199629b8829" >> Server: nginx >> Content-Length: 6713 >> Last-Modified: Tue, 11 Sep 2012 21:22:48 GMT >> Client-Date: Tue, 11 Sep 2012 21:23:19 GMT >> Client-Peer: 127.0.0.1:80 >> Client-Response-Num: 1 >> >> put with cannedacl forpublic works on this object. >> > As it should. I was referring to setacl with canned acl. > > Yehuda -- ----- Pozdrawiam Sławek "sZiBis" Skowron -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
