Known issues

This section documents known issues found in this release of IBM Storage Ceph S3 Object Browser.

Legal hold update fails

Legal hold operations can fail with an error message indicating that the update could not be completed. This issue occurs when attempting to enable or disable legal hold on an object. As a result, the legal hold state is not updated.

Currently there is no workaround.

(IBMCEPH-14376)

Incorrect object encryption status display

The S3 Object Browser can display the encryption status of an object as disabled even when encryption is enabled. This issue occurs when viewing object details. As a result, the encryption status shown in the UI does not reflect the actual object configuration.

As a workaround, verify the encryption status by using backend tools or APIs if required.

(IBMCEPH-14381)

Upload fails when encryption configuration is missing

Object uploads can fail when server-side encryption is enabled but the required encryption configuration is not available on the cluster. This issue occurs when selecting an encryption type such as SSE-KMS without corresponding cluster configuration. As a result, uploads fail.

As a workaround, ensure that the required encryption configuration is available before enabling encryption settings.

(IBMCEPH-14390)

Object Browser becomes unresponsive for large uploads

The S3 Object Browser can become unresponsive when uploading a very large number of objects. This issue occurs when uploading large directories with many objects and nested subdirectories. As a result, the UI might stop responding or the browser might crash.

To avoid this issue, upload objects in smaller batches.

(IBMCEPH-14382)

Lifecycle rule does not support noncurrent version expiration

Lifecycle rules do not provide an option to configure expiration for noncurrent object versions. As a result, lifecycle policies for expiring previous object versions cannot be defined through the S3 Object Browser.

Currently there is no workaround.

(IBMCEPH-14058)

Object search requires exact case match

Object search results are case sensitive and require an exact match of the object name . This issue occurs when searching with different capitalization. As a result, objects are not returned unless the case matches exactly.

As a workaround, ensure that the search string matches the exact case of the object name.

(IBMCEPH-13808)