Red Hat SummitCe contenu n'est pas disponible dans la langue sélectionnée.
Chapter 6. Asynchronous errata updates
This section describes the bug fixes, known issues, and enhancements of the z-stream releases.
6.1. Red Hat Ceph Storage 8.1z1
Red Hat Ceph Storage release 8.1z1 is now available. The security updates and bug fixes that are included in the update are listed in the RHSA-2025:11749 advisory.
6.2. Red Hat Ceph Storage 8.1z2
Red Hat Ceph Storage release 8.1z2 is now available. The bug fixes that are included in the update are listed in the RHBA-2025:14015 and RHBA-2025:13981 advisories.
6.3. Red Hat Ceph Storage 8.1z3
Red Hat Ceph Storage release 8.1z3 is now available. The bug fixes that are included in the update are listed in the RHBA-2025:17047 and RHBA-2025:17048 advisories.
6.3.1. Enhancements
This section lists all the major updates, and enhancements introduced in this release of Red Hat Ceph Storage.
6.3.1.1. Ceph Object Gateway
Enhanced conditional operations
This enhancement introduces support for conditional PUT and DELETE operations, including bulk and multi-delete requests. These conditional operations improve data consistency for some workloads.
The conditional InitMultipartUpload is not implemented in this release.
Bugzilla:2375001, Bugzilla:2383253
Rate limits now applied for LIST and DELETE request
LIST and DELETE requests are sub-operations of GET and PUT, respectively, but are typically more resource-intensive.
With this enhancement, it is now possible to configure rate limits for LIST and DELETE requests independently or in conjunction with existing GET and PUT rate limits. This provides more flexible granularity in managing system performance and resource usage.
6.4. Red Hat Ceph Storage 8.1z4
Red Hat Ceph Storage release 8.1z4 is now available. The bug fixes that are included in the update are listed in the the RHSA-2025:21068 and RHSA-2025:21203 advisories.
6.4.1. Known issues
This section documents known issues found in this release of Red Hat Ceph Storage.
6.4.1.1. The Cephadm utility
QAT cannot be used for TLS offload or acceleration mode together with SSL set
Enabling QAT on HAProxy with SSL enabled injects legacy OpenSSL engine directives. The legacy OpenSSL engine path breaks the TLS handshake, emitting the tlsv1 alert internal error error. With the TLS handshake broken, the TLS termination fails.
As a workaround, disable the QAT at HAProxy in order to keep the TLS handshake. Set the configuration file specifications as follows:
-
haproxy_qat_support: false -
ssl: true
As a result, QAT is disabled and the HAProxy TLS works as expected.
Under heavy connection rates higher CPU usage may be seen versus QAT-offloaded handshakes.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}