Hi, I just tried the first upgrade in a single node cluster (18.2.7 --> 18.2.8) and would like to share a few notes. The staggered upgrade should handle non-existing daemons a bit smoother. Before upgrading OSDs one has to upgrade the crash service first: ceph orch upgrade start --image quay.io/ceph/ceph:v18.2.8 --daemon-types crash --limit 1 Initiating upgrade to quay.io/ceph/ceph:v18.2.8 And then the upgrade fails: ceph health detail HEALTH_ERR Upgrade: failed due to an unexpected exception [ERR] UPGRADE_EXCEPTION: Upgrade: failed due to an unexpected exception Unexpected exception occurred during upgrade process: division by zero This is because there are no crash services running. Not sure how common this is, but maybe another check is required if there even are daemons of the specified type. Or at least add some details to the health output. Besides that, the limit parameter doesn't apply to all services. I reported that a few weeks ago (https://lists.ceph.io/hyperkitty/list/ceph-users@ceph.io/message/6TF5EOBGWCI...). Apart from that, the upgrade was successful on my lab cluster, so thanks for the great work! Regards, Eugen Zitat von Yuri Weinstein via ceph-users <ceph-users@ceph.io>:

We're happy to announce the 8th, and expected to be last, backport release in the Reef series. We recommend that all users update to this release.

We recommend users to update to this release. For detailed release notes with links & changelog please refer to the official blog entry at https://ceph.io/en/news/blog/2026/v18-2-8-reef-released/

Known Issues ------------ * During QA for v18.2.8, it was found that there was a bug for upgrades from Pacific to Reef. Pacific OSDs (and other Ceph daemons) were still using a deprecated connection feature bit that was adopted to indicate a Reef OSD. This can cause a OSD_UPGRADE_FINISHED warning before all OSDs are actually upgraded to Reef. There are no known issues associated with Pacific and Reef OSDs interoperating where Pacific OSDs are "advertising" Reef compatibility; however, out of an abundance of caution, we no longer recommend upgrading from Pacific to Reef directly.

Security Fixes -------------- * CephFS Client: A fix was merged to prohibit unprivileged users from modifying the sgid or suid bits on a file. Previously, unprivileged users were inadvertently permitted to set these bits if they were the sole bits being modified. * Mgr Alerts: The SMTP SSL context was enforced in the mgr/alerts module to resolve a security vulnerability (GHSA-xj9f-7g59-m4jx).

Notable Changes --------------- * RGW (RADOS Gateway): - Fixed an issue where bucket rm --bypass-gc was mistakenly removing head objects instead of tail objects, potentially causing data inconsistencies. - Fixed rgw-restore-bucket-index to handle objects with leading hyphens and to process versioned buckets correctly. - Addressed an issue in the msg/async protocol that caused memory locks and hangs during connection shutdown. - RGW STS: Made JWKS URL verification configurable for AWS compliance via the rgw_enable_jwks_url_verification configuration.

* CephFS / MDS: - Prevented the MDS from stalling (up to 5 seconds) during rename/stat workloads by forcing the log to nudge for unstable locks after early replies. - Fixed cephfs-journal-tool so it no longer incorrectly resets the journal trim position during disaster recovery, which was causing stale journal objects to linger forever in the metadata pool. - Fixed a bug where ll_walk incorrectly processed absolute paths as relative paths. - Prevented the ceph fs volume create command from accidentally deleting user-created pools if the command aborted during cleanup. - MDS Batched Operations: Added a new mds_allow_batched_ops configuration option (default: true) to control whether the MDS can batch lookup or getattr RPCs. - CephFS Subvolumes: Added the ceph fs subvolume snapshot getpath command to allow users to retrieve the absolute path of a snapshot of a subvolume.

* BlueStore: - Fixed a bug where the bytes_written_slow performance counter incorrectly reported 0 when using aio_write.

Getting Ceph ------------ * Git at git://github.com/ceph/ceph.git * Tarball at https://download.ceph.com/tarballs/ceph-18.2.7.tar.gz * Containers at https://quay.io/repository/ceph/ceph * For packages, see https://docs.ceph.com/en/latest/install/get-packages/ * Release git sha1: efac5a54607c13fa50d4822e50242b86e6e446df _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io