Yes- I was on Ceph 18.2.0 - I had to update the ceph.repo file in /etc/yum.repos.d to point to 18.2.1 to get the latest ceph client. Mean while the initial pull using --image worked flawlessly, so all my services were updated.
- Rob -----Original Message----- From: Matthew Vernon <mver...@wikimedia.org> Sent: Tuesday, December 19, 2023 4:32 AM To: ceph-users@ceph.io Subject: [ceph-users] Re: v18.2.1 Reef released On 19/12/2023 06:37, Eugen Block wrote: > Hi, > > I thought the fix for that would have made it into 18.2.1. It was > marked as resolved two months ago > (https://tracker.ceph.com/issues/63150, > https://github.com/ceph/ceph/pull/53922). Presumably that will only take effect once ceph orch is version 18.2.1 (whereas the reporter is still on 18.2.0)? i.e. one has to upgrade to 18.2.1 before this bug will be fixed and so the upgrade _to_ 18.2.1 is still affected. Regards, Matthew _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-le...@ceph.io _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-le...@ceph.io
