Forbidden error when using ceph-demo and accessing radosgw through API about ceph-container

[leseb]

I can reproduce your problem, however I'm not good enough with rados gateway to help you debugging this. You will have more luck on the Ceph user mailing list.

I don't think it's a container issue, it's just a feeling though I can't confirm that.
We are following the default steps to bootstrap rados gateway, nothing fancy at all.

[Ulexus]

I agree with @leseb in that I doubt this is a container problem. I do have some experience with trying to use the S3 compatibility layer, however. I have found it to be finicky about the bucket names. Try using an upper-case first bucket character; then, if that still fails, try an upper-case bucket name without any special characters (i.e., remove the dashes).

[ink1]

Thank you both. I have asked for help on the ceph user list.
The problem is not limited to bucket creation, it is more general. Eg. listing buckets does not work too

for bucket in conn.get_all_buckets():
    print "{name}\t{created}".format(
        name = bucket.name,
        created = bucket.creation_date,
    )

[leseb]

Ok thanks for reporting this. Closing this issue now :).

[ink1]

That's fine. I can confirm that this is not a ceph-docker issue. Everything is fine.
It's just it seems that radosgw-admin adds escape characters to the keys as in the example above

pARGxDCQ+D3fS+s6EQjeCGWLnEhMWdbncXeB\/hQu

Python does not need escape char for forward slash therefore resulting in the wrong secret key (one char longer). In this case the solution is simply to drop the back slash

aws_secret_access_key='pARGxDCQ+D3fS+s6EQjeCGWLnEhMWdbncXeB/hQu'

and everything works! No dark magic.

[leseb]

Weird I was thinking about this, but I generated a key like this: 5lVVZy0tmx5fVjwKCCbxjfocleFKZlOQ0ezrqeFf and got the error as well.

Maybe I made a mistake during my copy/paste.
Glad to hear that it works now :).

[ink1]

I've also added the following to /etc/ceph/ceph.conf

[client.radosgw.gateway]
host = scintel
keyring = /var/lib/ceph/radosgw/scintel/keyring
rgw socket path = /var/run/ceph/ceph-client.radosgw.gateway.asok
log file = /var/log/radosgw/ceph-client.radosgw.gateway.log
rgw frontends = "civetweb port=80"
rgw print continue = false
rgw enable apis = s3, swift, admin

I'll try deleting this and restarting rgw

[ink1]

No difference. S3 and Swift APIs must be enabled by default. So it's just a matter of getting the key right.

[kneufeld]

For future googlers, my issue was that rgw_dns_name didn't match the hostname of the url I was connecting too. ie: I was trying to curl s3.example.com but but config was as below:

[client.radosgw.gateway]
    rgw_dns_name = host1.example.com