SUSE Storage v1.11.1 Release Notes

This release introduces several improvements and bug fixes that are intended to improve system quality, resilience, stability and security. The documentation is available at SUSE Storage Documentation.

For terminology and context on SUSE Storage releases, see Releases.

Deprecations

V2 Backing Image deprecation

The Backing Image feature for the V2 Data Engine is now deprecated in v1.11.0 and is scheduled for removal in v1.12.0.

Users using V2 volumes for virtual machines are encouraged to adopt the Containerized Data Importer (CDI) for volume population instead.

#12237

Primary Highlights

V2 Data Engine

Now in technical preview stage

We are pleased to announce that the V2 Data Engine has officially graduated to the Technical Preview stage. This indicates increased stability and feature maturity as we move toward General Availability.

Limitation: While the engine is in Technical Preview, live upgrade is not supported yet. V2 volumes must be detached (offline) before engine upgrade.

Support for ublk front-end

Users can now configure ublk (Userspace Block Device) as the front-end for V2 Data Engine volumes. This provides a high-performance alternative to the NVMe-oF front-end for environments running Kernel v6.0+.

#11039

V1 Data Engine

Faster replica rebuilding from multiple sources

The V1 Data Engine now supports parallel rebuilding. When a replica needs to be rebuilt, the engine can now stream data from multiple healthy replicas simultaneously rather than a single source. This reduces the time required to restore redundancy for volumes containing tons of scattered data chunks.

#11331

General

Balance-aware algorithm disk selection for replica scheduling

SUSE Storage improves the disk selection for the replica scheduling by introducing an intelligent balance-aware scheduling algorithm, reducing uneven storage usage across nodes and disks.

#10512

Node disk health monitoring

SUSE Storage now actively monitors the physical health of the underlying disks used for storage by using S.M.A.R.T. data. This allows administrators to identify issues and raise alerts when abnormal SMART metrics are detected, helping prevent failed volumes.

#12016

Share manager networking

Users can now configure an extra network interface for the Share Manager to support complex network segmentation requirements.

#10269

ReadWriteOncePod (RWOP) support

Full support for the Kubernetes ReadWriteOncePod access mode has been added.

#9727

StorageClass allowedTopologies support

Administrators can now use the allowedTopologies field in SUSE Storage StorageClasses to restrict volume provisioning to specific zones, regions or nodes within the cluster.

#12261

Important Fixes

This release includes several critical stability fixes.

SUSE Storage workload pods memory leak

Fixed a critical regression where proxy connection leaks in the longhorn-instance-manager pods caused high memory consumption.

For more details, see #12575.

Backup and restore compatibility fix

Resolved compatibility issues introduced by aws-go-sdk v2, including backups to S3-compatible storage (like Storj or Google Cloud Storage). This fix ensures the completion of large data transfers to remote backup targets with correct authorization.

For more details, see #12714 and #12688.

V2 Data Engine (SPDK) refinements

Several enhancements were delivered for certain V2 Data Engine features, including fast replica rebuild and clone.

For more details, see #12751 and #12748.

CSI scheduling enhancement

Support CSI topology-aware PV nodeAffinity control.

For more details, see #12689 and #12656.

Installation

Ensure that your cluster is running Kubernetes v1.25 or later before installing SUSE Storage v1.11.1.

You can install SUSE Storage using a variety of tools, including SUSE® Rancher Prime, Kubectl, and Helm. For more information about installation methods and requirements, see Quick Installation in the documentation.

Upgrade

Ensure that your cluster is running Kubernetes v1.25 or later before upgrading from SUSE Storage v1.10.x or v1.11.0 to v1.11.1.

Users on v1.11.0 who experienced the memory leaks of longhorn-instance-manager pods #12575 are highly encouraged to upgrade to v1.11.1 to receive the permanent fix for the proxy connection leaks.

SUSE Storage only allows upgrades from supported versions. For more information about upgrade paths and procedures, see Upgrade in the documentation.

Post-release Known Issues

For information about issues identified after this release, see Release-Known-Issues.

Resolved Issues in This Release

Improvement

  • #12751 [BACKPORT][v1.11.1][IMPROVEMENT] Ensure V2 Engine ReplicaAdd respects the fast-replica-rebuild-enabled setting

  • #12689 [BACKPORT][v1.11.1][IMPROVEMENT] Topology-aware PV nodeAffinity control: allowedTopologies keys + strictTopology

  • #12585 [BACKPORT][v1.11.1][IMPROVEMENT] detailed log for the reason of node controller deleting backing image copies

  • #12711 [BACKPORT][v1.11.1][IMPROVEMENT] Relax endpoint-network-for-rwx-volume validation for migratable block-mode volumes

  • #12694 [BACKPORT][v1.11.1][IMPROVEMENT] RBAC permissions for csi-resizer

Bug

  • #12768 [BACKPORT][v1.11.1][BUG] Failed replicas accumulate during engine upgrade

  • #12748 [BACKPORT][v1.11.1][BUG] V2 Volume Clone Status is Changed Over Time

  • #12714 [BACKPORT][v1.11.1][BUG] Backup to S3 fails at 95%

  • #12738 [BACKPORT][v1.11.1][BUG] spdk_tgt encountered an assertion failure in longhorn-spdk-helper during a CI test run

  • #12688 [BACKPORT][v1.11.1][BUG] Google Cloud Storage (GCS) backup target always fails with SignatureDoesNotMatch due to AWS SDK Go v2 CRC32 checksum incompatibility

  • #12730 [BACKPORT][v1.11.1][BUG] Enable to set defaultSettings.nodeDiskHealthMonitoring

  • #12704 [BACKPORT][v1.11.1][BUG] stale name variable in nsmounter get_pid

  • #12665 [BACKPORT][v1.11.1][BUG] After upgrading to 1.11.0, new persistent volumes have nodeAffinity

  • #12661 [BACKPORT][v1.11.1][BUG] Incorrect storage double-counting causes scheduling failure when multiple replicas exist on the same node

  • #12641 [BACKPORT][v1.11.1][BUG] Recreated block disk with same name never becomes schedulable after volume and disk deletion

  • #12618 [BACKPORT][v1.11.1][BUG] SUSE Storage v1.10 Volume API is not compatible with the v1.8.1 manifest

  • #12626 [BACKPORT][v1.11.1][BUG] [V2] Can not use partition as block device

  • #12615 [BACKPORT][v1.11.1][BUG] Volume.Spec.CloneMode is empty after upgrading to v1.10.x and following version

  • #12589 [BACKPORT][v1.11.1][BUG] SUSE Storage validating webhook blocks k3s server node joins - flannel CNI fails to initialize

  • #12575 [BACKPORT][v1.11.1][BUG] V1.11.0 very high memory consumption for the instance manager

  • #12780 [BACKPORT][v1.11.1][BUG] Backing image data source pod fails when HTTP proxy is enabled

  • #12788 [BACKPORT][v1.11.1][BUG] orphan controller does not cleanup the instance on the corresponding instance manager on a multiple IM node

Stability

  • #12733 [BACKPORT][v1.11.1][BUG] Potential NEP in Volume Metrics Collector