Hi Gunnar, Not sure if I can give an authoritative answer! But we have been using cephadm for a longtime, did a lot of upgrades and rarely take care of updating the host packages at the same time as the containers (ceph orch upgrade). So it's somewhat the opposite of what you plan: the host packages (not used at all by the cluster, including cephadm which is a mgr module) are late compared to the cluster version. The only minor issue I have seen once was that the ceph command on the host was not supporting some new options introduced. 'cephadm shell' was an easy workaround until we upgraded the packages. I'm pretty sure it would work the same if you have a more recent version for the host packages. These tools use the Ceph API and there new clients can work with old servers and vice-versa (except for the few new things introduced in the API). Best regards, Michel Le 23/05/2025 à 09:33, Bandelow, Gunnar a écrit :

Hi everyone out there,

i have a hopefully simple to answer question: For example a reef cluster with cephadm and all containers and packages on version 18.2.4 on debian12 nodes.

The nodes itself have now ceph debian package upgrades available for the ceph packages with version 18.2.7.

Do I have to maintain the same version between the version within the containers and the OS? Can I just upgrade the nodes with a newer version  of packages and keep the containers at 18.2.4?

I marked ceph-common and cephadm as hold, because I wasn't sure, but now I want to know.

Any input is appreciated.

Best regards, Gunnar

=======================================================

Gunnar Bandelow (dipl. phys.)

Universitätsrechenzentrum (URZ) Universität Greifswald Felix-Hausdorff-Straße 18 17489 Greifswald Germany

_______________________________________________ ceph-users mailing list --ceph-users@ceph.io To unsubscribe send an email toceph-users-leave@ceph.io