-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rados admin client can't find keyring #824
Comments
the default admin key is |
The keying is not located there on the rados gateway. And the config file /etc/ceph/ceph.conf references a different path (there is a key ring at that path). And the name of the client section in the config file is wrong. But my key issue is that trying to use the admin client to create users fails, saying it can't locate the key ring.
|
The rados gateway key is in |
I'm aware of that. But the admin client isn't finding it despite the /var/lib... being specified in the ceph.conf file.
|
Please share the command you're trying to execute along with the output. |
Here's the example output:
I'm following the docs here: |
For sanity, I checked that the admin client is reading the config file with
So, it reads the config file but doesn't pull out the path. Here's the config file:
Note that the section header is |
If I copy the keyring to
but I run into a different issue:
|
I understand all of your issues and they are perfectly normal. You might have to install some rgw package to get the |
Yep, okay, so I installed the
Thanks @leseb! I'd like to contribute to docs to help other avoid some of the pitfalls I've been stumbling into. Is it appropriate to put a section in the README for how to use the gateway? Or is it worth creating a |
@rnowling Would be nice to get more docs I agree, would you mind updating the content of the wiki? |
It would be my pleasure! |
:) |
When I try to run the rados admin client, it can't find the keyring. I check the
/etc/ceph/ceph.conf
config file. I think it should be[client.radosgw...]
(to match the docs), not [client.rgw...]
but changing that didn't solve the issue.The text was updated successfully, but these errors were encountered: