RHBA-2025:1889 - Bug Fix Advisory

Topic

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

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):

• Previously, the `thinPoolConfig.overprovisionRatio` field in the `LVMCluster` custom resource (CR) could be configured only during the creation of the `LVMCluster` CR. With this release, you can now update the `thinPoolConfig.overprovisionRatio` field even after creating the `LVMCluster` CR.
• Support for configuring metadata size for the thin pool: This feature provides the following new optional fields in the `LVMCluster` custom resource (CR):
• `thinPoolConfig.metadataSizeCalculationPolicy`: Specifies the policy to calculate the metadata size for the underlying volume group. You can set this field to either `Static` or `Host`. By default, this field is set to `Host`.
• `thinPoolConfig.metadataSize`: Specifies the metadata size for the thin pool. You can configure this field only when the `MetadataSizeCalculationPolicy` field is set to `Static`.

This erratum corrects the following issues:

• Previously, LVM Storage prevented allocating more than 90% of a disk’s size to the thin pool. This fix removes the limitation, allowing disk allocation above 90% to the thin pool. This fix also introduces warnings to alert users about potential risks when using this configuration.
• Previously, LVM Storage excluded all devices specified by the user through the `paths` field or `the optionalPaths` field if a non-existing device was configured at the top of the list. With this fix, LVM Storage correctly determines the state of each specified device and includes it in the volume group creation.
• Previously, LVM Storage wiped data during an upgrade from OCP 4.16 to OCP 4.18 if the `forceWipeDevicesAndDestroyAllData` field was set to `true`. This fix corrects the behavior by implementing a migration logic that prevents unintentional data wipes.

This erratum includes various maintainability and debuggability improvements.

After a successful LVMS upgrade, the latest lvms-operator SHA image is available.

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.18 for RHEL 9 x86_64
• Red Hat OpenShift Container Platform for Power 4.18 for RHEL 9 ppc64le
• Red Hat OpenShift Container Platform for IBM Z and LinuxONE 4.18 for RHEL 9 s390x
• Red Hat OpenShift Container Platform for ARM 64 4.18 for RHEL 9 aarch64

Fixes

• OCPBUGS-38929 - LVMS thin pool used size percent configuration should allow values over 90%
• OCPBUGS-41632 - LVMCluster failing with RAID disk created via mdadm
• OCPBUGS-42385 - Wiping of local volume functionality failed on Multi-node cluster
• OCPBUGS-43910 - LVMCluster fails to found storage device link
• OCPBUGS-44377 - Unintentionally wiping data during an upgrade on LVMS
• OCPEDGE-1152 - LVMS Maintainability and Debugability 4.18
• OCPEDGE-1226 - Make thin pool metadata size configurable in LVMS
• OCPEDGE-1243 - Make thin pool overprovisionRatio editable in LVMS

CVEs

• CVE-2019-12900
• CVE-2020-11023
• CVE-2022-49043
• CVE-2024-12085
• CVE-2024-12797
• CVE-2024-45338
• CVE-2025-0750

References

(none)