RHBA-2024:0763 - Bug Fix Advisory

Topic

Updated container images that add new features and fix multiple bugs are now available for LVMS 4.15

Description

Logical volume manager storage creates thin-provisioned volumes using the
Logical Volume Manager and provides dynamic provisioning of block storage
on a cluster.

Enhancement(s):

• Recovering volume groups from the previous LVMS installation - With this release, `LVMCluster` custom resource (CR) provides support for recovering volume groups from the previous LVMS installation. If the `deviceClasses.name` field is set to the name of a volume group from the previous LVMS installation, LVMS recreates the resources related to that volume group in the current LVMS installation. This simplifies the process of using devices from the previous LVMS installation through the re-installation of LVMS.
• Support for wiping the devices in LVMS - This feature provides a new optional field `forceWipeDevicesAndDestroyAllData` in the `LVMCluster` custom resource (CR) to force wipe the selected devices. Prior to this release, wiping the devices required manually accessing the host. With this release, you can force wipe the disks without manual intervention. This simplifies the process of wiping the disks.

WARNING: If `forceWipeDevicesAndDestroyAllData` is set to `true`, LVMS wipes all previous data on the devices. You must use this feature with caution.

• Support for deploying LVMS on multi-node clusters - This feature provides support for deploying LVMS on multi-node clusters. Prior to this release, LVMS only supported single-node configurations. With this release, LVMS supports all the Red Hat OpenShift Container Platform deployment topologies. This enables provisioning of local storage on multi-node clusters.

WARNING: LVMS only supports node local storage on multi-node clusters. It does not support storage data replication mechanisim across nodes. When you are using LVMS on multi-node clusters, you must ensure storage data replication through active or passive replication mechanism to avoid single point of failure.

• Integrating RAID arrays with LVMS - This feature provides support for integrating RAID arrays that are created using the `mdadm` utility with LVMS. The `LVMCluster` custom resource (CR) provides support for adding paths to the RAID arrays in the `deviceSelector.paths` field and the `deviceSelector.optionalPaths` field.
• FIPS Compliance - With this release, LVMS is designed for Federal Information Processing Standards (FIPS). When LVMS is installed on Red Hat OpenShift Container Platform in FIPS mode, LVMS uses the RHEL cryptographic libraries that have been submitted to NIST for FIPS 140-3 validation on only the x86_64 architecture.

After successful LVMS upgrade from 4.15, the latest lvms-operator SHA image
should be seen.

Users of LVMS are advised to upgrade to the latest version in
OpenShift Container Platform, which fixes these bugs and adds these
enhancements.

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

• Red Hat OpenShift Container Platform 4.15 for RHEL 9 x86_64
• Red Hat OpenShift Container Platform for Power 4.15 for RHEL 9 ppc64le
• Red Hat OpenShift Container Platform for IBM Z and LinuxONE 4.15 for RHEL 9 s390x
• Red Hat OpenShift Container Platform for ARM 64 4.15 for RHEL 9 aarch64

Fixes

• OCPBUGS-11486 - Extend leaseDurationSeconds in SNO
• OCPBUGS-13558 - LVMS: After node loss, lvmCluster resource still has the entry for the lost node
• OCPBUGS-15576 - 4.13 LVMS: PVC stuck pending when applying whole LVMS deployment config in a single List
• OCPBUGS-17805 - LVMS: Not seeing 'NotEnoughCapacity' events on Multi-node cluster
• OCPBUGS-17848 - LVM degrades with paths already part of vg
• OCPBUGS-17853 - expectedVGCount / readyVGCount mismatch in MultiNode Clusters fails Readiness
• OCPBUGS-18354 - LVMS: Watches / Owns Configuration missing for some dependents of LVM Operator
• OCPBUGS-23181 - topolvm-node crash loopback errors due to default device-class not detected properly
• OCPBUGS-23191 - LVM Controller not respecting Tolerations while counting VGs created
• OCPBUGS-23375 - [LVMS] After OCP upgrade old lvms resource pods still present in 'Error' state
• OCPBUGS-23409 - [LVMS] After OCP upgrade along with lvms upgrade workload annotations are missing in topolvm-controller deployment
• OCPBUGS-23995 - LVMS: LVMCluster without any valid optionalPaths remains in "Progressing" instead of "Failed" state
• OCPBUGS-24396 - overprovisionRatio can not be set to 1
• OCPBUGS-24586 - FIPS scan failure - lvms-must-gather container missing dependent openssl version
• OCPBUGS-24600 - Workload annotations are missing in the pod spec
• OCPBUGS-27003 - lvmcluster creation using diskselector with symlink (by-id) and wipe option fails
• OCPBUGS-27219 - Workload annotation missing in lvms namespace causing LVMS installation failure
• OCPEDGE-26 - Wipe local filesystem with LVMS
• OCPEDGE-37 - TopoLVM: Support PVCs in smaller Increments than 1Gi
• OCPEDGE-45 - LVMS Maintainability and Debugability 4.15
• OCPEDGE-63 - LVMS FIPS Build and Delivery Compliance
• OCPEDGE-64 - Enable multi-node LVMS
• OCPEDGE-670 - LVMS 4.15 Release
• OCPEDGE-70 - Software RAID via mdadm on LVMS
• OCPEDGE-77 - LVMS Support for OpenShift without CSISnapshot Capability
• OCPEDGE-81 - Recover LVMS cluster from on-disk metadata
• OCPBUGS-27330 - [release-4.15] LVMS deployment.kubernetes.io/revision in topolvm-controller container is continously patched out
• OCPBUGS-27358 - [release-4.15] LVM Operator does not have update and patch rights for various Cluster scoped resources
• OCPBUGS-26768 - PVC provisioning fails with storageClass using default volumeGroup in a cluster where multiple VGs are present
• OCPBUGS-27820 - [LVMS] FIPS build compliance check payload scan failed on lvms operator
• OCPBUGS-18397 - Deletion of LVMCluster is stuck when VG no longer exists and doesn't remove lvmd conf entry for deviceClass
• OCPBUGS-18708 - Creating more than one LVMCluster is allowed but not working
• OCPBUGS-19990 - Name of a device class should not be allowed to change
• OCPBUGS-22109 - [LVMS] PVC warning event 'notEnoughCapacity' is not generated
• OCPBUGS-22362 - Build is missing "valid subscription" data - LVM Storage [4.15]
• OCPBUGS-28966 - After an upgrade from 4.14 to 4.15, LVMS cannot tag the existing volume groups
• OCPBUGS-29065 - During an upgrade, TopoLVM Node volumes are not reconciled

CVEs

(none)

References

(none)