Chapter 8. Asynchronous errata updates

Learn about bug fixes for Ceph File System included in this release.

With this fix, the code now checks whether the buffer contains data before dumping it, and explicitly dumps an empty string when the buffer length is zero. This prevents spurious empty buffer entries and ensures safe handling of xattr values. As a result, xattr dumps are cleaner and more accurate, and the MDS no longer crashes in this scenario.

(IBMCEPH-12883)

With this fix, the CephFS client API is now invoked without holding the GIL. As a result, subvolume operations in the volumes module can progress normally even when an asynchronous clone operation is running. (IBMCEPH-12760)

With this fix, the logic now returns early when the MDRequestRef is NULL, instead of attempting to dereference it.

As a result, crashes caused by this condition are prevented, improving overall MDS stability.

(IBMCEPH-12900)

Learn about bug fixes for Ceph Object Gateway included in this release.

With this fix, the code has been updated to ensure proper handling when both bucket_index_max_shards and the bucket’s num_shards are set to 0. As a result, object unlink operations now succeed in this scenario.

(IBMCEPH-12915)

With this fix, the system now processes topics in batches of 1,000, ensuring that all topics are eventually processed rather than cycling over only the initial set. As a result, bucket notifications are now sent for all topics, and topic queues no longer fill up or block service operation.

(IBMCEPH-12914)

Get to know the known issues for ​Ceph Object Gateway multi-site found in this release.

As a result, some omap entries may remain in the bucket index. In cases that many leftover keys accumulate, the following error is emitted: (27) File too large. This inconsistency can affect tools or processes that depend on accurate bucket index listings.

As a workaround:

Red Hat Ceph Storage clusters now support cluster deployments on ARM 64 (aarch64), IBM POWER, and S390x architectures. This enhancement enables you to consume Ceph storage from cost‑effective AWS Graviton instances and other ARM‑based platforms.

(ISCE-1400)

With this change, applications that use OAuth2 through python‑oauthlib can enforce PKCE as part of the authorization process, improving overall authentication security.

(IBMCEPH-12630)

The improvement groups lifecycle rules that share the same prefix and object tag conditions, allowing Object Gateway to enumerate objects and fetch tags only once instead of performing multiple passes for each rule. This reduces unnecessary I/O and improves concurrency during lifecycle execution.

As a result, lifecycle operations complete faster and more predictably for large buckets with complex lifecycle configurations, improving overall efficiency in high‑scale environments.

(IBMCEPH-13353)

Previously, the command always installed required system packages and dependencies, even in environments where hosts were already preconfigured or managed by external tools.

With this fix, cephadm prepare-host now supports more flexible host preparation behavior, allowing administrators to better align dependency management with their existing provisioning and automation workflows.

(IBMCEPH-13460)

Previously, playbooks that relied on the ceph_config module could not run successfully, even though the same playbooks worked as expected in earlier releases. This regression prevented automation workflows and tests from retrieving or updating Ceph configuration values through Ansible.

With this fix, the ceph_config module is resolved correctly, and cephadm‑ansible playbooks that depend on this module now run successfully as expected.

(IBMCEPH-13542)

Previously, gRPC clients that rely on reflection were unable to discover service descriptors automatically, which caused requests to fail unless the service definition was provided explicitly.

With this fix, the gRPC reflection capability is available as expected. gRPC clients can now discover service descriptors dynamically, enabling standard tooling and workflows to interact with the service without requiring manual proto file configuration.

(IBMCEPH-13627)

Previously, this caused confusion by suggesting that a release candidate or debug build was running, even though the cluster was using a supported production image.

With this fix, the Ceph version string now correctly reflects the production build status after upgrading to RHCS 9.

(IBMCEPH-13276)

Previously, directory listing operations could fail when both encryption and case‑insensitive directory features were enabled, even though the data existed and permissions were correctly configured.

With this fix, directory contents can now be listed successfully when encryption and case‑insensitive directory support are enabled together.

(IBMCEPH-13452)

Previously, these errors could occur during normal S3 operations, including GET requests, even when no conflicting client activity was expected.

With this fix, Ceph Object Gateway handles concurrent access scenarios more reliably, reducing unexpected request failures and improving consistency for S3 client operations.

(IBMCEPH-13756)

This inconsistency could lead applications to incorrectly assume that objects were unavailable after validating their existence.

With this fix, GET requests for multipart‑uploaded objects now behave consistently, ensuring reliable access to objects uploaded using multipart upload.

(IBMCEPH-13618)

Previously, Ceph Object Gateway could enter an error state during startup, preventing object storage services from becoming available after the upgrade.

With this fix, Ceph Object Gateway initializes successfully following the upgrade, restoring object storage availability and normal administrative operations.

(IBMCEPH-13877)

In Red Hat Ceph Storage 8.x, changes to Alertmanager template rendering no longer guarantee the presence of this variable. As a result, template rendering can fail with an undefined variable error, preventing Alertmanager from redeploying and pausing the upgrade.

When this issue occurs, the upgrade remains paused, the cluster enters a HEALTH_WARN state, and the upgrade cannot continue until the configuration is corrected.

As a workaround, update the custom Alertmanager template to replace references to default_webhook_urls with webhook_urls, and then resume the upgrade. After the template is updated, the Alertmanager service redeploys successfully and the upgrade completes.

(IBMCEPH‑12929)

Affected upgrade paths: Upgrade from Red Hat Ceph Storage 8.1z5 to any of the following versions: 9.0, 9.0z1, 9.0z2

As a workaround, upgrade together with the --allowerasing tag.

With this tag, the libcephfs-daemon package gets uninstalled and the upgrade proceeds successfully.

(IBMCEPH-13912)

If many stale entries accumulate, operations that depend on accurate bucket index listings can be affected. In some cases, tools that read the bucket index might report errors, such as (27) File too large.

This issue can impact administrative operations or background processes that rely on consistent bucket index metadata after lifecycle expiration runs on versioned buckets.

As a workaround, administrators can use available Object Gateway tooling to scan for and remove leftover bucket index entries.

(IBMCEPH-12980)