SUSE Storage v1.10.2 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.

Important fixes

This release includes several critical stability fixes.

RWX volume unavailable after node drain

Fixed a race condition where ReadWriteMany (RWX) volumes could remain in the attaching state after node drains, causing workloads to become unavailable.

For more details, see #12231.

Encrypted volume cannot be expanded online

Fixed an where online expansion of encrypted volumes did not propagate the new size to the dm-crypt device.

For more details, see #12368.

Cloned volume cannot be attached to workload

Fixed a bug where cloned volumes could fail to reach a healthy state, preventing attachment to workloads.

For more details, see #12208.

Block mode volume migration stuck

Fixed a regression in block-mode volume migrations where newly created replicas could incorrectly inherit the lastFailedAt timestamp from source replicas, causing repeated deletion and blocking migration completion.

For more details, see #12312.

Replica auto balance disk pressure threshold stalled

Fixed an issue where replica auto-balance under disk pressure could be blocked if stopped volumes were present on the disk.

For more details, see #12334.

Replicas accumulate during engine upgrade

Fixed a bug where temporary replicas could accumulate during engine upgrade. High etcd latency could cause new replicas to fail verification, leading to accumulation over multiple reconciliation cycles.

For more details, see #12115.

Potential client connection and context leak

Fixed potential context leaks in the instance manager client and backing image manager client, improving stability and preventing resource exhaustion.

For more details, see #12200 and #12195.

Replica node level soft anti-affinity ignored

Fixed a bug of replica scheduling loop where replicas could be scheduled onto nodes that already host a replica, even when Replica Node-Level Soft Anti-Affinity was disabled.

For more details, see #12251.

Installation

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

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.9.x to v1.10.2.

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

Feature

  • #12245 [BACKPORT][v1.10.2][FEATURE] Inherit namespace for longhorn-share-manager in FastFailover mode

  • #12181 [BACKPORT][v1.10.2][FEATURE] [Dependency] aws-sdk-go v1.55.7 is EOL as of 2025-07-31 — plan to migrate to V2?

Improvement

  • #12329 [BACKPORT][v1.10.2][IMPROVEMENT] Fix V2 Volume CSI Clone Slowness Caused by VolumeAttachment Webhook Blocking

Bug

  • #12536 [BACKPORT][v1.10.2][BUG] instance-manager on nodes that do not have hard or solid state disk DDOSing cluster DNS server with TXT query _grpc_config.localhost

  • #12518 [BACKPORT] Replica rebuild, clone and restore fail, traffic being sent to HTTP proxy

  • #12512 [BACKPORT][v1.10.2][BUG] Healthy replica could be deleted unexpectedly after reducing volume’s number of replicas

  • #12509 [BACKPORT][v1.10.2][BUG] Data locality enabled volume fails to remove an existing running replica after numberOfReplicas reduced

  • #12479 [BACKPORT][v1.10.2][BUG] System backup may fail to be created or deleted

  • #12222 [BACKPORT][v1.10.2][BUG] Some default settings in questions.yaml are placed incorrectly.

  • #12482 [BACKPORT][v1.10.2][BUG] Auto balance feature may lead to volumes falling into a replica deletion-recreation loop

  • #12494 [BACKPORT][v1.10.2][BUG] Single replica volume could get stuck in attaching/detaching loop after the replica node rebooted

  • #12200 [BACKPORT][v1.10.2][BUG] Potential Instance Manager Client Context Leak

  • #12476 [BACKPORT][v1.10.2][BUG] SnapshotBack proxy request might be sent to incorrect instance-manager pod

  • #12451 [BACKPORT][v1.10.2][BUG] Unknown OS condition in node CR is not properly removed during upgrade

  • #12231 [BACKPORT][v1.10.2][BUG] RWX volume becomes unavailable after drain node

  • #12382 [BACKPORT][v1.10.2][BUG] mounting error is not properly hanedled during CSI node publish volume

  • #12368 [BACKPORT][v1.10.2][BUG] Encrypted Volume Cannot Be Expanded Online

  • #12357 [BACKPORT][v1.10.2][BUG] The auo generated backing image pod name is complained by kubelet

  • #12342 [BACKPORT][v1.10.2][BUG] tests.test_cloning.test_cloning_basic fails at msater-head

  • #12208 [BACKPORT][v1.10.2][Bug] A cloned volume cannot be attached to a workload

  • #12312 [BACKPORT][v1.10.2][BUG] Block Mode Volume Migration Stuck

  • #12334 [BACKPORT][v1.10.2][BUG] Replica auto balance disk pressure threshold stalled with stopped volumes

  • #12270 [BACKPORT][v1.10.2][BUG] short name mode is enforcing, but image name longhornio/longhorn-manager:v1.10. │ │ 0 returns ambiguous list

  • #12115 [BACKPORT][v1.10.2][BUG] Replicas accumulate during engine upgrade

  • #12195 [BACKPORT][v1.10.2][BUG] Potential BackingImageManagerClient Connection and Context Leak

  • #12251 [BACKPORT][v1.10.2][BUG] SUSE Storage ignores Replica Node Level Soft Anti-Affinity when auto balance is set to best-effort

  • #12234 [BACKPORT][v1.10.2][BUG] Invalid memory address or nil pointer dereference (again)

  • #12213 [BACKPORT][v1.10.2][BUG] Request Header Or Cookie Too Large in Web UI with OIDC auth