Issued:
2024-09-05
Updated:
2024-09-05

RHBA-2024:6398 - Red Hat OpenShift Data Foundation 4.14.10 Bug Fix Update

Synopsis

Red Hat OpenShift Data Foundation 4.14.10 Bug Fix Update

Type/Severity

Bug Fix Advisory None

Topic

Updated images that fix several bugs are now available for Red Hat OpenShift Data Foundation 4.14.10 on Red Hat Enterprise Linux 9 from Red Hat Container Registry.

Description

Red Hat OpenShift Data Foundation is software-defined storage integrated with and optimized for the Red Hat OpenShift Data Foundation. Red Hat OpenShift Data Foundation is a highly scalable, production-grade persistent storage for stateful applications running in the Red Hat OpenShift Container Platform. In addition to persistent storage, Red Hat OpenShift Data Foundation provisions a multi-cloud data management service with an S3-compatible API.

Bug fixes:

  • Previously, Multus was marked as Tech preview in the Security and network section of OpenShift Data Foundation management console user interface while using Create StorageSystem option even though Multus was Generally Available with OpenShift Data Foundation 4.14. The Tech preview tag is removed with this fix. (BZ#2270492)

  • Previously, changing a bucketclass' placement policy resulted in an error. With this fix, it is now possible to change a bucketclass' placement policy. (BZ#2272084)

  • Previously, the handling of ENOENT for reading and heading objects was counted as an error. As a result, after a few occurrences of such error, the NameSpace resource was moved to the Rejected state. With this fix, the errors returned from the underlying store are fine tuned. (BZ#2274284)

  • Previously, when trying to use persistent volume (PV) pool, xattr are used to save metadata of objects. However, updates to that metadata fails as Filesystem on PV does not support xattr. With this fix, there is a failback if Filesystem does not support xattr and metadata is saved in a file. (BZ#2278619)

  • Previously, HEAD-request returned the HTTP 200 Code for the prefix path instead of 404 from the API With this fix, ENOENT is thrown when object is a directory and the key is missing the trailing '/'. As a result, the head-object operation on a prefix results in a 404 error. (BZ#2282213)

  • Previously, the ls command in AWS command line interface (CLI) took long time. With this fix, for Postgres queries, the extra DB query after processing the results of the first query is avoided. As a result, the ls command works as expected. (BZ#2284399)

  • Previously, the Multicloud Object Gateway bucket lifecycle policy did not delete all objects. With this fix, lifecycle will continue deleting the matching objects. (BZ#2291128)

  • Previously, starting from OpenShift Data Foundation 4.14, the legacy OSDs were crashing in the init container that resized the OSD. This was because, the legacy OSDs that were created in OpenShift Container Storage 4.3 and since upgraded to a future version might have failed. With this fix, the crashing resize init container was removed from the OSD pod spec. As a result, the legacy OSD starts, however it is recommended that the legacy OSDs are replaced soon. (BZ#2276533)

All users of Red Hat OpenShift Data Foundation are advised to upgrade to these updated images, which provide these bug fixes.

Solution

Before applying this update, make sure all previously released errata relevant to your system have been applied.

For details on how to apply this update, refer to:

https://access.redhat.com/articles/11258

Affected Products

ProductVersionArch
Red Hat OpenShift Data Foundation4x86_64
Red Hat OpenShift Data Foundation for RHEL 9 ARM4aarch64
Red Hat OpenShift Data Foundation for IBM Z and LinuxONE4s390x
Red Hat OpenShift Data Foundation for IBM Power, little endian4ppc64le

Fixes

CVEs

References

(none)

Additional information