- Issued:
- 2021-08-30
- Updated:
- 2021-08-30
RHBA-2021:3312 - Bug Fix Advisory
Synopsis
Red Hat OpenShift Container Storage 4.8.1 bug fix update
Type/Severity
Bug Fix Advisory
Topic
Updated images that fix several bugs are now available for Red Hat OpenShift Container Storage 4.8.1 on Red Hat Enterprise Linux 8 from Red Hat Container Registry.
Description
Red Hat OpenShift Container Storage is software-defined storage integrated with and optimized for the Red Hat OpenShift Container Platform. Red Hat OpenShift Container Storage 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 Container Storage provisions a multicloud data management service with an S3 compatible API.
Bug Fix(es):
- Improved backend vault parameter configuration allows configuring of the `VAULT_BACKEND` parameter for selecting the type of backend used by Hashicorp Vault. The autodetection of the backend used by Hashicorp Vault is not always working as expected. In case, if a non-common configuration is used, the automatically detected configuration parameter might be set incorrectly. By allowing users to configure the `VAULT_BACKEND` (or `vaultBackend`) parameter, non-common configurations can now be forced to use a particular type of backend. (BZ#1984333)
- Previously, while upgrading from OpenShift Container Storage v4.6 to v4.7, the Multicloud Object Gateway (MCG) exposed the Prometheus metrics only from its core pod as the old route was not removed, and thus provides incorrect information on the MCG health status. With this update, during the OpenShift Container Storage upgrade, the old route is removed, and the Prometheus metrics provide accurate information on the health status of all the MCG pods. (BZ#1989557)
- Previously, it was not possible to deploy the Multicloud Object Gateway (MCG) with other storage classes as the noobaa-db pod consumed storage from the `ocs-ceph-rbd` storage class. With this update, you can set the noobaa-db storageclass name from the Storage Cluster CR. This allows MCG deployment without storage consumption from the `ocs-ceph-rbd` as the Storage Cluster spec includes `DbStorageClassName` in the `MultiCloudGatewaySpec`. (BZ#1977329)
All users of OpenShift Container Storage are advised to upgrade to these updated packages, 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:
Affected Products
- Red Hat OpenShift Data Foundation 4 for RHEL 8 x86_64
- Red Hat OpenShift Data Foundation for IBM Power, little endian 4 for RHEL 8 ppc64le
- Red Hat OpenShift Data Foundation for IBM Z and LinuxONE 4 for RHEL 8 s390x
Fixes
- BZ - 1977329 - [RFE] Allow DBStorageClass to be set from Storage Cluster CR for Noobaa
- BZ - 1984282 - [GSS] [4.8 clone] Standalone Object Gateway is failing to connect
- BZ - 1984333 - [RFE] [4.8 clone] VAULT_BACKEND parameter should be added to the csi-kms-connection-details(will require doc updates)
CVEs
References
(none)
The Red Hat security contact is secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.