RHBA-2024:4181 - Bug Fix Advisory

Topic

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

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

• Support for configuring thick-provisioned storage - This feature provides support for configuring thick-provisioned storage. If you exclude the deviceClasses.thinPoolConfig field in the LVMCluster custom resource (CR), logical volumes are thick provisioned. Thick provisioned volumes do no support volume cloning and VolumeSnapshotClass. Therefore, CSI snapshotting is not supported.
• Support for a new warning message when device selector is not configured in the LVMCluster custom resource - This update provides a new warning message when you do not configure the deviceSelector field in the LVMCluster CR.
• Support for adding encrypted devices to a volume group - This feature provides support for adding encrypted devices to a volume group. With this release, you can specify the path to the LUKS encrypted device in the deviceSelector field in the LVMCluster CR.

This erratum corrects the following issues:

• Previously, some LVMVolumeGroupNodeStatus operands were not deleted on the cluster during the deletion of the LVMCluster CR. With this release, deleting the LVMCluster CR triggers the deletion of all the LVMVolumeGroupNodeStatus operands.
• Previously, LVM Storage uninstallation was stuck waiting for the deletion of the LVMVolumeGroupNodeStatus operands. This fix corrects the behavior by ensuring all operands are deleted, allowing LVM Storage to be uninstalled without delay.
• Previously, LVM Storage created persistent volume claims (PVCs) with storage size requests that were not multiples of the disk sector size. This can cause issues during LVM2 volume creation. This fix corrects the behavior by rounding the storage size requested by PVCs to the nearest multiple of 512.
• Previously, the LVMCluster CR contained an excluded status element for a device that is set up correctly. This fix filters the correctly set device from being considered for an excluded status element, so it only appears in the ready devices.
• Previously, LVM Storage did not support minimum storage size for persistent volume claims (PVCs). This can lead to mount failures while provisioning PVCs. With this release, LVM Storage supports minimum storage size for PVCs. The following are the minimum storage sizes that you can request for each file system type: block: 8 MiB, xfs: 300 MiB, ext4: 32 MiB
• Previously, TopoLVM did not have a file watcher for the lvmd configuration. As a result, any updates to the lvmd configuration were not applied until the next restart. With this release, the lvmd configuration on nodes running LVMS is hot-reloaded. This triggers a restart of LVMS when changes to the lvmd configuration are detected.
• Previously, the TopoLVM controllers deployed during LVMCluster CR setup were separate from the LVMS controllers. As a result, memory and CPU usage were higher. With this release, the TopoLVM controllers have been merged into the LVMS controllers, significantly reducing memory and CPU usage.

After a successful LVMS upgrade, 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.16 for RHEL 9 x86_64
• Red Hat OpenShift Container Platform for Power 4.16 for RHEL 9 ppc64le
• Red Hat OpenShift Container Platform for IBM Z and LinuxONE 4.16 for RHEL 9 s390x
• Red Hat OpenShift Container Platform for ARM 64 4.16 for RHEL 9 aarch64

Fixes

• OCPBUGS-26502 - lvmcluster creation using diskselector with symlink (by-id) and wipe option fails
• OCPBUGS-27226 - LVM Operator does not have update and patch rights for various Cluster scoped resources
• OCPBUGS-27331 - LVMS deployment.kubernetes.io/revision in topolvm-controller container is continously patched out
• OCPBUGS-27365 - [LVMS] PV mount on Pod failed
• OCPBUGS-27956 - PVC provisioning fails with storageClass using default volumeGroup in a cluster where multiple VGs are present
• OCPBUGS-28975 - After an upgrade from 4.14 to 4.15, LVMS cannot tag the existing volume groups
• OCPBUGS-29188 - LVMCluster tries to filter already used devices if they are symlinked and causes Status Messages to be present
• OCPBUGS-29225 - LVMS does not update SCCs when the SCCs already exist before reconciliation
• OCPBUGS-30032 - LVMS: can't provision a Filesystem PVC when byte-level precision resources.requests.storage is not a multiple of 512
• OCPBUGS-30346 - Feature Annotations for CSV are missing in LVMS Summary causing CVP Failures
• OCPEDGE-27 - Hot reload lvmd config file
• OCPEDGE-689 - MicroLVMS - LVMS / TopoLVM Controller Consolidation
• OCPEDGE-82 - Support using encrypted devices
• OCPEDGE-999 - Thick Provisioning: Enable LVMCluster configurations without thinPoolConfig
• OCPEDGE-60 - LVMS Maintainability and Debugability 4.16
• OCPBUGS-27095 - Workload annotation missing in lvms namespace causing LVMS installation failure
• OCPBUGS-30266 - LVMS: FailedMount a small (10Mi) Filesystem PVC
• OCPBUGS-30830 - [LVMS] After OCP multi-node upgrade LVMCluster CR stuck in 'Progressing' state
• OCPBUGS-32268 - LVMS image based FBC in repo not synced to previous releases
• OCPBUGS-32753 - LVMS operator uninstall from console hangs forever deleting operands
• OCPBUGS-32954 - Removing LVMCluster CR does not trigger the removal of LVMVolumeGroupNodeStatus CRs
• OCPBUGS-33026 - Fix LVMS operator meta-data
• OCPBUGS-35404 - [release-4.16] Thin Pool Chunk Size is static and does not allow pool size above 32TiB

CVEs

• CVE-2023-6597
• CVE-2023-45288
• CVE-2023-45290
• CVE-2024-0450
• CVE-2024-3651
• CVE-2024-24783

References

(none)