Hello,
Thanks for your answering ! We finally managed to connect with the admin
keyring
but we think that is not the best practice. A few later after your
message, there was another one
which indicates a way to get a real client. We shall try it and get you
advised of the result.
Best regards
JM
Le 19/07/2022 à 10:50, Kai Stian Olstad a écrit :
On 08.07.2022 16:18, Jean-Marc FONTANA wrote:
We're planning to use rbd too and get block device for a linux server.
In order to do that, we installed ceph-common packages
and created ceph.conf and ceph.keyring as explained at Basic Ceph
Client Setup — Ceph Documentation
<https://docs.ceph.com/en/pacific/cephadm/client-setup/>
(https://docs.ceph.com/en/pacific/cephadm/client-setup/)
This does not work.
Ceph seems to be installed
$ dpkg -l | grep ceph-common
ii ceph-common 16.2.9-1~bpo11+1 amd64 common
utilities to mount and interact with a ceph storage cluster
ii python3-ceph-common 16.2.9-1~bpo11+1 all Python
3 utility libraries for Ceph
$ ceph -v
ceph version 16.2.9 (4c3647a322c0ff5a1dd2344e039859dcbd28c830)
pacific (stable)
But, when using commands that interact with the cluster, we get this
message
$ ceph -s
2022-07-08T15:51:24.965+0200 7f773b7fe700 -1 monclient(hunting):
handle_auth_bad_method server allowed_methods [2] but i only support
[2,1]
[errno 13] RADOS permission denied (error connecting to the cluster)
The default user for ceph is the admin/client.admin do you have that
key in your keyring?
And is the keyring file readable for the user running the ceph commands?
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
