Thanks! That helped.
It turns out the other issue was that I was running the admin command on
the gateway node when I should have been running on the monitor node.
On Wed, Jun 1, 2016 at 5:06 PM, LOPEZ Jean-Charles
wrote:
> Looks like I missed the paste:
> http://docs.ceph.com/docs/master/man/
Looks like I missed the paste:
http://docs.ceph.com/docs/master/man/8/ceph/#options
There you have the options available from the command line.
In your case the user id is radosgw-rgw0 so the command line should be
radosgw-admin --id radosgw.rgw0 usage show or radosgw-admin --name
client.rados
I did use ceph-ansible to deploy the gateway -- using the default
settings. It should work out of the box but does not.
So... can the radosgw-admin CLI utility take a keyring path in the conf
file or does the path need to be manually specified?
And secondly, after copying the keyring to one of t
Hi,
radosgw-admin is not radosgw. It’s the RADDOS Gateway cli admin utility.
All ceph components by default use the client.admin user name to connect to the
Ceph cluster. If you deployed the radosgw, the gateway itself was properly
configured by Ansible and the files were placed where they have
Hi all,
I'm trying to set up a Ceph cluster with an S3 gateway using the
ceph-ansible playbooks. I'm running into an issue where the radosgw-admin
client can't find the keyring. The path to the keyring is listed in the
ceph.conf file. I confirmed with strace that the client opens the conf
file
