On Tue, Jun 3, 2025 at 7:08 AM Sake Ceph <ceph@paulusma.eu> wrote:
This is also the case with us for Cephfs clients. We use the kernel mount, but still you need to install ceph-common. Which isn't possible with the latest version of Reef and thus those are stuck on 18.2.4. Or am I doing something wrong?
The version of ceph-common on the client side is much less relevant, especially if you are using the kernel client. I wouldn't expect any issues with upgrading the cluster while leaving ceph-common on the client side as is. Technically, it's possible to mount the kernel client without ceph-common being installed at all. Thanks, Ilya
Op 03-06-2025 06:03 CEST schreef Dmitry Melekhov <dm@belkam.com>:
03.06.2025 00:30, Albert Shih пишет:
Le 02/06/2025 à 15:59:00+0400, Dmitry Melekhov a écrit Hi,
02.06.2025 15:39, Michel Jouvin пишет:
I don't think it is useful to report that you have the problem... Everybody trying to deploy the RPMs on RHEL or any of its derivative will have the issue until 9.6 is released... 9.6 is released some time ago:
cat /etc/redhat-release AlmaLinux release 9.6 (Sage Margay) I just like to understand what are the advantage to deploy directly on the OS and not through docker/podman container ? Is it just the history ?
This server is client to cluster .
Because as I understand with container you will have no issue isn't it ?
No, you are wrong, 17.2.9 has no container build. _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io