Issued:
2022-09-14
Updated:
2022-09-14

RHBA-2022:6525 - Red Hat OpenShift Data Foundation 4.11.1 Bug Fix Update

Synopsis

Red Hat OpenShift Data Foundation 4.11.1 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.11.1 on Red Hat Enterprise Linux 8 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 multicloud data management service with an S3 compatible API.

Bug fix(es):

  • Previously, if you created a new restored Persistent Volume Claim (PVC) from a volume snapshot whose size was the same as the volume snapshot, the restored PVC would fail if the parent PVC was resized after you took the volume snapshot, and before you created the new restored PVC. With this update, the CephCSI does not do any checks to validate the size of the volume when you create a clone, which resolves the issue. (BZ#2120927)

  • Previously, you would see an empty dashboard if you navigated to the OpenShift Data Foundation dashboard pages as the non-admin users did not have read and write access in the openshift-storage namespace. With this update, hiding the "Data Foundation" tab resolves the issue. (BZ#2116262)

  • Previously, entries were created in the Database (DB) in such a way that the latest key was not reflected correctly. This happened because there was a race between several PUT operations to the same key. With this update, fixing the inserts as well as the existing entries on the upgrade resolves the issue. (BZ#2111544)

  • Previously, there was a small leak of a handler on each PUT operation. With this update, catching the handler and releasing it resolves the issue. (BZ#2111847)

  • With this update, you can add settings to rotate the log file according to the periodicity and maxLogSize. In the storageCluster Custom Resource (CR) you can add the LogCollector inside spec which contains fields such as enable (to enable or disable logs collector), maxLogSize(to rotate the log after this assigned size, the minimum value is 500M), and periodicity (to set the time interval at which it will rotate. Valid inputs are daily, hourly, weekly, monthly). If both the maxLogSizeandperiodicity` are applied, whichever comes first is given more priority. (BZ#2117146)

  • With this update, you can now rotate logs based on the size. There is a new field in the Ceph cluster Custom Resource (CR) inside the logCollectorSpec named maxLogSize that indicates the size of the maximum log after which the log is rotated. (BZ#2116416)

  • Previously, two MONs could end up on the same node instead of being spread across unique nodes. This happened when the operator was restarted in the middle of a MON failover, multiple MONs could be started on the same node, which reduced the MON quorum availability. With this update, the operator properly cancels the MON failover if the MON failover times out, and ensures that any extra MONs are removed based on the stretch topology or multiple MONs that run on the same node. (BZ#2120598)

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 IBM Z and LinuxONE4s390x
Red Hat OpenShift Data Foundation for IBM Power, little endian4ppc64le

Fixes

CVEs

References

(none)

Additional information