v18.2.4 Reef released
We're happy to announce the 4th release in the Reef series. An early build of this release was accidentally exposed and packaged as 18.2.3 by the Debian project in April. That 18.2.3 release should not be used. The official release was re-tagged as v18.2.4 to avoid further confusion. v18.2.4 container images, now based on CentOS 9, may be incompatible on older kernels (e.g., Ubuntu 18.04) due to differences in thread creation methods. Users upgrading to v18.2.4 container images with older OS versions may encounter crashes during `pthread_create`. For workarounds, refer to the related tracker. However, we recommend upgrading your OS to avoid this unsupported combination. Related tracker: https://tracker.ceph.com/issues/66989 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/2024/v18-2-4-reef-released/ Notable Changes --------------- * RADOS: This release fixes a bug (https://tracker.ceph.com/issues/61948) where pre-reef clients were allowed to connect to the `pg-upmap-primary` (https://docs.ceph.com/en/reef/rados/operations/read-balancer/) interface despite users having set `require-min-compat-client=reef`, leading to an assert in the osds and mons. You are susceptible to this bug in reef versions prior to 18.2.3 if 1) you are using an osdmap generated via the offline osdmaptool with the `--read` option or 2) you have explicitly generated pg-upmap-primary mappings with the CLI command. Please note that the fix is minimal and does not address corner cases such as adding a mapping in the middle of an upgrade or in a partially upgraded cluster (related trackers linked in https://tracker.ceph.com/issues/61948). As such, we recommend removing any existing pg-upmap-primary mappings until remaining issues are addressed in future point releases. See https://tracker.ceph.com/issues/61948#note-32 for instructions on how to remove existing pg-upmap-primary mappings. * RBD: When diffing against the beginning of time (`fromsnapname == NULL`) in fast-diff mode (`whole_object == true` with `fast-diff` image feature enabled and valid), diff-iterate is now guaranteed to execute locally if exclusive lock is available. This brings a dramatic performance improvement for QEMU live disk synchronization and backup use cases. * RADOS: `get_pool_is_selfmanaged_snaps_mode` C++ API has been deprecated due to being prone to false negative results. It's safer replacement is `pool_is_in_selfmanaged_snaps_mode`. * RBD: The option ``--image-id`` has been added to `rbd children` CLI command, so it can be run for images in the trash. Related tracker: https://tracker.ceph.com/issues/65393 Getting Ceph ------------ * Git at git://github.com/ceph/ceph.git * Tarball at https://download.ceph.com/tarballs/ceph_18.2.4.orig.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: e7ad5345525c7aa95470c26863873b581076945d
Hi Yuri et al, The email announcement includes the fix for 61948, but the linked blog page omits it entirely. Suggest adding that note to the blog page. The language used also differs slightly between the two announcements. email:
We're happy to announce the 4th release in the Reef series. blog: | This is the third backport release in the Reef series. We recommend | that all users update to this release.
On Wed, Jul 24, 2024 at 02:12:25PM -0700, Yuri Weinstein wrote:
We're happy to announce the 4th release in the Reef series. ... Notable Changes --------------- * RADOS: This release fixes a bug (https://tracker.ceph.com/issues/61948) where pre-reef clients were allowed to connect to the `pg-upmap-primary` (https://docs.ceph.com/en/reef/rados/operations/read-balancer/) interface despite users having set `require-min-compat-client=reef`, leading to an assert in the osds and mons. You are susceptible to this bug in reef versions prior to 18.2.3 if 1) you are using an osdmap generated via the offline osdmaptool with the `--read` option or 2) you have explicitly generated pg-upmap-primary mappings with the CLI command. Please note that the fix is minimal and does not address corner cases such as adding a mapping in the middle of an upgrade or in a partially upgraded cluster (related trackers linked in https://tracker.ceph.com/issues/61948). As such, we recommend removing any existing pg-upmap-primary mappings until remaining issues are addressed in future point releases. See https://tracker.ceph.com/issues/61948#note-32 for instructions on how to remove existing pg-upmap-primary mappings. This is the missing item on the webpage.
-- Robin Hugh Johnson Gentoo Linux: Dev, Infra Lead, Foundation President & Treasurer E-Mail : robbat2@gentoo.org GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136
Robin, thx We will fix the typo On Wed, Jul 24, 2024 at 5:18 PM Robin H. Johnson <robbat2@gentoo.org> wrote:
Hi Yuri et al,
The email announcement includes the fix for 61948, but the linked blog page omits it entirely.
Suggest adding that note to the blog page.
The language used also differs slightly between the two announcements.
email:
We're happy to announce the 4th release in the Reef series. blog: | This is the third backport release in the Reef series. We recommend | that all users update to this release.
On Wed, Jul 24, 2024 at 02:12:25PM -0700, Yuri Weinstein wrote:
We're happy to announce the 4th release in the Reef series. ... Notable Changes --------------- * RADOS: This release fixes a bug (https://tracker.ceph.com/issues/61948) where pre-reef clients were allowed to connect to the `pg-upmap-primary` (https://docs.ceph.com/en/reef/rados/operations/read-balancer/) interface despite users having set `require-min-compat-client=reef`, leading to an assert in the osds and mons. You are susceptible to this bug in reef versions prior to 18.2.3 if 1) you are using an osdmap generated via the offline osdmaptool with the `--read` option or 2) you have explicitly generated pg-upmap-primary mappings with the CLI command. Please note that the fix is minimal and does not address corner cases such as adding a mapping in the middle of an upgrade or in a partially upgraded cluster (related trackers linked in https://tracker.ceph.com/issues/61948). As such, we recommend removing any existing pg-upmap-primary mappings until remaining issues are addressed in future point releases. See https://tracker.ceph.com/issues/61948#note-32 for instructions on how to remove existing pg-upmap-primary mappings. This is the missing item on the webpage.
-- Robin Hugh Johnson Gentoo Linux: Dev, Infra Lead, Foundation President & Treasurer E-Mail : robbat2@gentoo.org GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136 _______________________________________________ Dev mailing list -- dev@ceph.io To unsubscribe send an email to dev-leave@ceph.io
Hi,
On 25 Jul 2024, at 00:12, Yuri Weinstein <yweinste@redhat.com> wrote:
We're happy to announce the 4th release in the Reef series.
The repo of reef now returns 404
GET /rpm-reef/el8/SRPMS/ HTTP/1.1 Host: download.ceph.com
< HTTP/1.1 404 Not Found If change the repo to previous version, the answer 200 as expected
GET /rpm-18.2.2/el8/SRPMS/ HTTP/1.1 Host: download.ceph.com
< HTTP/1.1 200 OK Seems something wrong with packages k
Hi, I have tried running simple update on Rocky 8.9 running reef 18.2.2, it's failing straight away. dnf update Ceph x86_64 84 B/s | 146 B 00:01 Errors during downloading metadata for repository 'Ceph': - Status code: 404 for https://download.ceph.com/rpm-reef/el8/x86_64/repodata/repomd.xml (IP: 158.69.68.124) Error: Failed to download metadata for repo 'Ceph': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried Can someone please suggest? Thanks, Amar On 25/07/24 09:57, Konstantin Shalygin wrote: EXTERNAL: Do not click links or open attachments if you do not recognize the sender. Hi, On 25 Jul 2024, at 00:12, Yuri Weinstein <yweinste@redhat.com><mailto:yweinste@redhat.com> wrote: We're happy to announce the 4th release in the Reef series. The repo of reef now returns 404 GET /rpm-reef/el8/SRPMS/ HTTP/1.1 Host: download.ceph.com < HTTP/1.1 404 Not Found If change the repo to previous version, the answer 200 as expected GET /rpm-18.2.2/el8/SRPMS/ HTTP/1.1 Host: download.ceph.com < HTTP/1.1 200 OK Seems something wrong with packages k _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io<mailto:ceph-users@ceph.io> To unsubscribe send an email to ceph-users-leave@ceph.io<mailto:ceph-users-leave@ceph.io> -- DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Thanks for your cooperation.
Use https://download.ceph.com/rpm-reef/el9/x86_64/ On Fri, Jul 26, 2024 at 1:37 AM Amardeep Singh <amardeep.singh@techblue.co.uk> wrote:
Hi,
I have tried running simple update on Rocky 8.9 running reef 18.2.2, it's failing straight away.
dnf update Ceph x86_64 84 B/s | 146 B 00:01 Errors during downloading metadata for repository 'Ceph': - Status code: 404 for https://download.ceph.com/rpm-reef/el8/x86_64/repodata/repomd.xml (IP: 158.69.68.124) Error: Failed to download metadata for repo 'Ceph': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
Can someone please suggest?
Thanks,
Amar
On 25/07/24 09:57, Konstantin Shalygin wrote:
EXTERNAL: Do not click links or open attachments if you do not recognize the sender.
Hi,
On 25 Jul 2024, at 00:12, Yuri Weinstein <yweinste@redhat.com><mailto:yweinste@redhat.com> wrote:
We're happy to announce the 4th release in the Reef series.
The repo of reef now returns 404
GET /rpm-reef/el8/SRPMS/ HTTP/1.1 Host: download.ceph.com
< HTTP/1.1 404 Not Found
If change the repo to previous version, the answer 200 as expected
GET /rpm-18.2.2/el8/SRPMS/ HTTP/1.1 Host: download.ceph.com
< HTTP/1.1 200 OK
Seems something wrong with packages k _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io<mailto:ceph-users@ceph.io> To unsubscribe send an email to ceph-users-leave@ceph.io<mailto:ceph-users-leave@ceph.io>
--
DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system.
If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Thanks for your cooperation. _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
Are you saying that the el9 rpms work on el8 hosts? The complaint so far is that a minor release in Ceph has silently and unexpectedly seemed to remove support for an OS version that is still widely deployed. If this was intentional, there is a question as to why it didn't even warrant a note in the "notable changes" section of the release notes. I'm sure that people can switch operating system versions, but this is a non-trivial amount of effort that should have been clearly indicated that it was coming and expected. Ideally this sort of drop of OS support would only come with a major version change, say the v19 release, not in a bugfix point release. As for me, I've got 40 hosts that suddenly need non-trivial maintenance to get us to a reasonable place, given that all users are recommended to update to 18.2.4. -- Adam On 7/26/24 8:41 AM, Yuri Weinstein wrote:
This email originated from outside of K-State.
Use https://download.ceph.com/rpm-reef/el9/x86_64/
On Fri, Jul 26, 2024 at 1:37 AM Amardeep Singh <amardeep.singh@techblue.co.uk> wrote:
Hi,
I have tried running simple update on Rocky 8.9 running reef 18.2.2, it's failing straight away.
dnf update Ceph x86_64 84 B/s | 146 B 00:01 Errors during downloading metadata for repository 'Ceph': - Status code: 404 for https://download.ceph.com/rpm-reef/el8/x86_64/repodata/repomd.xml (IP: 158.69.68.124) Error: Failed to download metadata for repo 'Ceph': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
Can someone please suggest?
Thanks,
Amar
On 25/07/24 09:57, Konstantin Shalygin wrote:
EXTERNAL: Do not click links or open attachments if you do not recognize the sender.
Hi,
On 25 Jul 2024, at 00:12, Yuri Weinstein <yweinste@redhat.com><mailto:yweinste@redhat.com> wrote:
We're happy to announce the 4th release in the Reef series.
The repo of reef now returns 404
GET /rpm-reef/el8/SRPMS/ HTTP/1.1 Host: download.ceph.com
< HTTP/1.1 404 Not Found
If change the repo to previous version, the answer 200 as expected
GET /rpm-18.2.2/el8/SRPMS/ HTTP/1.1 Host: download.ceph.com
< HTTP/1.1 200 OK
Seems something wrong with packages k _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io<mailto:ceph-users@ceph.io> To unsubscribe send an email to ceph-users-leave@ceph.io<mailto:ceph-users-leave@ceph.io>
--
DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system.
If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Thanks for your cooperation. _______________________________________________ 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
I'll echo Adam's comments here. Moreover, if we take a step to perform in place upgrade from el8 to el9, will 18.2.2 compatible for el9 before upgrading to 18.2.4? This seems like too much effort for a minor release. Amar ________________________________ From: Adam Tygart <mozes@ksu.edu> Sent: 26 July 2024 19:27 To: ceph-users@ceph.io <ceph-users@ceph.io> Subject: [ceph-users] Re: [Ceph-announce] v18.2.4 Reef released EXTERNAL: Do not click links or open attachments if you do not recognize the sender. Are you saying that the el9 rpms work on el8 hosts? The complaint so far is that a minor release in Ceph has silently and unexpectedly seemed to remove support for an OS version that is still widely deployed. If this was intentional, there is a question as to why it didn't even warrant a note in the "notable changes" section of the release notes. I'm sure that people can switch operating system versions, but this is a non-trivial amount of effort that should have been clearly indicated that it was coming and expected. Ideally this sort of drop of OS support would only come with a major version change, say the v19 release, not in a bugfix point release. As for me, I've got 40 hosts that suddenly need non-trivial maintenance to get us to a reasonable place, given that all users are recommended to update to 18.2.4. -- Adam On 7/26/24 8:41 AM, Yuri Weinstein wrote:
This email originated from outside of K-State.
Use https://urldefense.com/v3/__https://download.ceph.com/rpm-reef/el9/x86_64/__...
On Fri, Jul 26, 2024 at 1:37 AM Amardeep Singh <amardeep.singh@techblue.co.uk> wrote:
Hi,
I have tried running simple update on Rocky 8.9 running reef 18.2.2, it's failing straight away.
dnf update Ceph x86_64 84 B/s | 146 B 00:01 Errors during downloading metadata for repository 'Ceph': - Status code: 404 for https://urldefense.com/v3/__https://download.ceph.com/rpm-reef/el8/x86_64/re... (IP: 158.69.68.124) Error: Failed to download metadata for repo 'Ceph': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
Can someone please suggest?
Thanks,
Amar
On 25/07/24 09:57, Konstantin Shalygin wrote:
EXTERNAL: Do not click links or open attachments if you do not recognize the sender.
Hi,
On 25 Jul 2024, at 00:12, Yuri Weinstein <yweinste@redhat.com><mailto:yweinste@redhat.com> wrote:
We're happy to announce the 4th release in the Reef series.
The repo of reef now returns 404
GET /rpm-reef/el8/SRPMS/ HTTP/1.1 Host: download.ceph.com
< HTTP/1.1 404 Not Found
If change the repo to previous version, the answer 200 as expected
GET /rpm-18.2.2/el8/SRPMS/ HTTP/1.1 Host: download.ceph.com
< HTTP/1.1 200 OK
Seems something wrong with packages k _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io<mailto:ceph-users@ceph.io> To unsubscribe send an email to ceph-users-leave@ceph.io<mailto:ceph-users-leave@ceph.io>
--
DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system.
If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Thanks for your cooperation. _______________________________________________ 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
ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Thanks for your cooperation.
We'd like to add our own noises of discontent from the public gallery. We have three Ceph clusters running Alma 8.10, a total of 108 nodes, storing ~40PiB of Science data. Upgrading these nodes to Alma/Rocky/OEL/RHEL 9.x is something we have been preparing for, but had not expected to do so for another 6 months. Why remove support for EL8 mid release cycle, with zero warning? Is there any possibility of getting one more point release of ceph for EL8? This would at least avoid a knee-jerk OS upgrade. Best regards Jake On 26/07/2024 15:37, Amardeep Singh wrote:
CAUTION: This email originated from outside of the LMB: .-ceph-users-bounces@ceph.io-. Do not click links or open attachments unless you recognize the sender and know the content is safe. If you think this is a phishing email, please forward it to phishing@mrc-lmb.cam.ac.uk --
I'll echo Adam's comments here.
Moreover, if we take a step to perform in place upgrade from el8 to el9, will 18.2.2 compatible for el9 before upgrading to 18.2.4?
This seems like too much effort for a minor release.
Amar
________________________________ From: Adam Tygart <mozes@ksu.edu> Sent: 26 July 2024 19:27 To: ceph-users@ceph.io <ceph-users@ceph.io> Subject: [ceph-users] Re: [Ceph-announce] v18.2.4 Reef released
EXTERNAL: Do not click links or open attachments if you do not recognize the sender.
Are you saying that the el9 rpms work on el8 hosts?
The complaint so far is that a minor release in Ceph has silently and unexpectedly seemed to remove support for an OS version that is still widely deployed. If this was intentional, there is a question as to why it didn't even warrant a note in the "notable changes" section of the release notes.
I'm sure that people can switch operating system versions, but this is a non-trivial amount of effort that should have been clearly indicated that it was coming and expected. Ideally this sort of drop of OS support would only come with a major version change, say the v19 release, not in a bugfix point release.
As for me, I've got 40 hosts that suddenly need non-trivial maintenance to get us to a reasonable place, given that all users are recommended to update to 18.2.4. -- Adam
On 7/26/24 8:41 AM, Yuri Weinstein wrote:
This email originated from outside of K-State.
Use https://urldefense.com/v3/__https://download.ceph.com/rpm-reef/el9/x86_64/__...
On Fri, Jul 26, 2024 at 1:37 AM Amardeep Singh <amardeep.singh@techblue.co.uk> wrote:
Hi,
I have tried running simple update on Rocky 8.9 running reef 18.2.2, it's failing straight away.
dnf update Ceph x86_64 84 B/s | 146 B 00:01 Errors during downloading metadata for repository 'Ceph': - Status code: 404 for https://urldefense.com/v3/__https://download.ceph.com/rpm-reef/el8/x86_64/re... (IP: 158.69.68.124) Error: Failed to download metadata for repo 'Ceph': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
Can someone please suggest?
Thanks,
Amar
On 25/07/24 09:57, Konstantin Shalygin wrote:
EXTERNAL: Do not click links or open attachments if you do not recognize the sender.
Hi,
On 25 Jul 2024, at 00:12, Yuri Weinstein <yweinste@redhat.com><mailto:yweinste@redhat.com> wrote:
We're happy to announce the 4th release in the Reef series.
The repo of reef now returns 404
GET /rpm-reef/el8/SRPMS/ HTTP/1.1 Host: download.ceph.com
< HTTP/1.1 404 Not Found
If change the repo to previous version, the answer 200 as expected
GET /rpm-18.2.2/el8/SRPMS/ HTTP/1.1 Host: download.ceph.com
< HTTP/1.1 200 OK
Seems something wrong with packages k _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io<mailto:ceph-users@ceph.io> To unsubscribe send an email to ceph-users-leave@ceph.io<mailto:ceph-users-leave@ceph.io>
--
DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system.
If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Thanks for your cooperation. _______________________________________________ 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
ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system.
If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Thanks for your cooperation. _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
For help, read https://www.mrc-lmb.cam.ac.uk/scicomp/ then contact unixadmin@mrc-lmb.cam.ac.uk -- Dr Jake Grimmett Head Of Scientific Computing MRC Laboratory of Molecular Biology Francis Crick Avenue, Cambridge CB2 0QH, UK. Phone 01223 267019 / Mobile 0776 9886539
Rook users are seeing OSDs fail on arm64 with v18.2.4. I would think it also affects non-rook users. Tracker opened: https://tracker.ceph.com/issues/67213 Thanks, Travis On Wed, Jul 24, 2024 at 3:13 PM Yuri Weinstein <yweinste@redhat.com> wrote:
We're happy to announce the 4th release in the Reef series.
An early build of this release was accidentally exposed and packaged as 18.2.3 by the Debian project in April. That 18.2.3 release should not be used. The official release was re-tagged as v18.2.4 to avoid further confusion.
v18.2.4 container images, now based on CentOS 9, may be incompatible on older kernels (e.g., Ubuntu 18.04) due to differences in thread creation methods. Users upgrading to v18.2.4 container images with older OS versions may encounter crashes during `pthread_create`. For workarounds, refer to the related tracker. However, we recommend upgrading your OS to avoid this unsupported combination. Related tracker: https://tracker.ceph.com/issues/66989
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/2024/v18-2-4-reef-released/
Notable Changes --------------- * RADOS: This release fixes a bug (https://tracker.ceph.com/issues/61948) where pre-reef clients were allowed to connect to the `pg-upmap-primary` (https://docs.ceph.com/en/reef/rados/operations/read-balancer/) interface despite users having set `require-min-compat-client=reef`, leading to an assert in the osds and mons. You are susceptible to this bug in reef versions prior to 18.2.3 if 1) you are using an osdmap generated via the offline osdmaptool with the `--read` option or 2) you have explicitly generated pg-upmap-primary mappings with the CLI command. Please note that the fix is minimal and does not address corner cases such as adding a mapping in the middle of an upgrade or in a partially upgraded cluster (related trackers linked in https://tracker.ceph.com/issues/61948). As such, we recommend removing any existing pg-upmap-primary mappings until remaining issues are addressed in future point releases. See https://tracker.ceph.com/issues/61948#note-32 for instructions on how to remove existing pg-upmap-primary mappings. * RBD: When diffing against the beginning of time (`fromsnapname == NULL`) in fast-diff mode (`whole_object == true` with `fast-diff` image feature enabled and valid), diff-iterate is now guaranteed to execute locally if exclusive lock is available. This brings a dramatic performance improvement for QEMU live disk synchronization and backup use cases. * RADOS: `get_pool_is_selfmanaged_snaps_mode` C++ API has been deprecated due to being prone to false negative results. It's safer replacement is `pool_is_in_selfmanaged_snaps_mode`. * RBD: The option ``--image-id`` has been added to `rbd children` CLI command, so it can be run for images in the trash.
Related tracker: https://tracker.ceph.com/issues/65393
Getting Ceph ------------ * Git at git://github.com/ceph/ceph.git * Tarball at https://download.ceph.com/tarballs/ceph_18.2.4.orig.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: e7ad5345525c7aa95470c26863873b581076945d _______________________________________________ Ceph-announce mailing list -- ceph-announce@ceph.io To unsubscribe send an email to ceph-announce-leave@ceph.io
participants (7)
-
Adam Tygart
-
Amardeep Singh
-
Jake Grimmett
-
Konstantin Shalygin
-
Robin H. Johnson
-
Travis Nielsen
-
Yuri Weinstein