Hi all,
while setting up a system with cephadm under Quincy, I bootstrapped from host A, added mons on hosts B
and C, and rebooted host A.
Afterwards, ceph seemed to be in a healthy state (no OSDs yet, of course), but my host A
was "offline".
I was afraid I had run into https://tracker.ceph.com/issues/51027, but no, my host A simply lacked the
ceph.pub key.
Since this is Quincy (no support for non-root users), I had provided the other mons by 'ssh-copy-id -f
-i /etc/ceph/ceph.pub root@hostB' etc. but not my host A.
After making up for that, my host A found itself to be online again ;-)
Then I prepared three machines to host OSDs. For some reasons, one of them showed only the locked
'/dev/sdX' devices and not the LVs that I intended to use as OSDs.
I rebooted, which did not change anything, then copied the key ('ssh-copy-id -f -i /etc/ceph/ceph.pub
root@fileserverA'), which did everything, and now I am wondering if I should write a cron job that
periodically copies the key to all involved machines...
Where could the keys get lost? Is this a container-feature?
Is it really true that sites using cephadm never reboot their nodes? Can't
really believe that.
Regards
Thomas
--
--------------------------------------------------------------------
Thomas Roth
Department: Informationstechnologie
Location: SB3 2.291
GSI Helmholtzzentrum für Schwerionenforschung GmbH
Planckstraße 1, 64291 Darmstadt, Germany, www.gsi.de
Commercial Register / Handelsregister: Amtsgericht Darmstadt, HRB 1528
Managing Directors / Geschäftsführung:
Professor Dr. Paolo Giubellino, Dr. Ulrich Breuer, Jörg Blaurock
Chairman of the Supervisory Board / Vorsitzender des GSI-Aufsichtsrats:
State Secretary / Staatssekretär Dr. Volkmar Dietz
_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
