Answering myself: The upstream guide has a bug. Instead of
ceph-bluestore-tool --dev $DEV_PATH set-label-key --key osd_key -v $COPIED_KEYRING
one has to put
ceph-bluestore-tool --dev $DEV_PATH set-label-key --key osd_key -v $ROTATED_KEY
et voilà...
That's the way. You can write a simple script getting the device path from ceph-volume and the osd_key from /var/lib/ceph/osd/ceph-X/keyring or from ceph auth get osd.X to set the bluestore value via ceph-bluestore-tool.
The cluster is in the same state as before, there's nothing to worry about. Have you tried adding the hostname after the fqdn in /etc/hosts? That's good practice after all and might help you with this problem.
Hi there!
I had to do the cephx keyring migration by hand since I have a Ceph cluster member which is not part of my PVE cluster. I followed the upstream guide from ceph.com and had a healthy cluster at some point. That is after I rebooted every...
Yeah sure, I was rather hoping for a list of mandatory actions that explains what needs to be done. Just to broaden the picture before I find myself diving into the code. That would of course be the ultimate way. There's also the upstream guide...
Could anyone point me to a resource which tells me what the helper script is doing internally so that I can follow those steps for an external Ceph cluster member which is neither a mon nor a PVE cluster member? The helper script says FAIL...