Re: OSDs not starting at boot after upgrade to Tentacle
OK, found it. The ExecStart line in /usr/lib/systemd/system/ceph-volume@.service is wrong in Tentacle. squid: ExecStart=/bin/sh -c 'timeout $CEPH_VOLUME_TIMEOUT /usr/sbin/ceph-volume-systemd %i' tentacle: ExecStart=/bin/sh -c 'timeout $CEPH_VOLUME_TIMEOUT @CMAKE_INSTALL_PREFIX@/sbin/ceph-volume-systemd %i' Obviously the @CMAKE_INSTALL_PREFIX@ isn't going to work in there... Reinstating the line as in squid brings it back to life. On 02/01/2026 16:35, Chris Palmer via ceph-users wrote:
I've just upgraded a Centos 9 Stream test cluster from squid 19.2.3 to tentacle 20.2.0. It is a non-cephadm package install. It all looked pretty good, except that now no OSD processes start automatically after a reboot:
* There have been no other changes whatever to the system other than ceph. * OSD processes would start automatically on squid. * After a reboot, all of the /var/lib/ceph/osd/ceph-n directories still exist but are empty. * A manual activation brings them all back to life (sudo ceph-volume lvm activate --all). * Nothing at all relevant in the ceph logs. * After a reboot, and before manually activating, /run/systemd/system is empty. After activation all of the /run/systemd/system/ceph-osd.target.wants symlinks are back in place, and the /var/lib/ceph/osd/ceph-n directories have been repopulated. * It is happening on every osd node. * As expected, after 10 minutes the osds are marked out (unless noout is set).
I really can't spot what is causing this. Can anyone give me any pointers?
Thanks, Chris _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
participants (1)
-
Chris Palmer