Hi,
I upgrade an ceph-cluster to 19.2.6 and still had the warning, that 1 client entities with insecure key types.
"ceph auth ls" show that client.admin is the only key with aes but the key in /etc/ceph/ceph.client.admin.keyring has allready an aes256 key.
But this key don't shows up in ceph auth ls.
Now the mistake took its course - I create an new key client.adminnew with the same rights
and then remove the key client.admin…
and now I'm in big trouble, because Im not able to recreate client.admin from the keyring /etc/ceph/ceph.client.admin.keyring because the mon is'nt accessible for me
Any help to fix this issue would be very very helpfull!
best regards
Udo
I upgrade an ceph-cluster to 19.2.6 and still had the warning, that 1 client entities with insecure key types.
"ceph auth ls" show that client.admin is the only key with aes but the key in /etc/ceph/ceph.client.admin.keyring has allready an aes256 key.
But this key don't shows up in ceph auth ls.
Now the mistake took its course - I create an new key client.adminnew with the same rights
Code:
client.adminnew
key: XXXXX/dqtSKvECAA2sY7OhKFhKHB/uwDKUQ6YuVOOp0Um3IYkfFTs3XXXXX=
caps: [mds] allow
caps: [mgr] allow *
caps: [mon] allow *
caps: [osd] allow *
and now I'm in big trouble, because Im not able to recreate client.admin from the keyring /etc/ceph/ceph.client.admin.keyring because the mon is'nt accessible for me
Code:
2026-11-13T17:43:15.929+0100 701cc3fff6c0 -1 monclient(hunting): handle_auth_bad_method failed to auth with my available methods: (13) Permission denied
[errno 13] RADOS permission denied (error connecting to the cluster)
Any help to fix this issue would be very very helpfull!
best regards
Udo