SUSE Storage v1.9.3 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 more information about release-related terminology, see Releases.

Installation

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

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 Installation in the documentation.

Upgrade

Ensure that your cluster is running Kubernetes v1.25 or later before upgrading from SUSE Storage v1.9.x (< v1.9.3) to v1.9.3. To upgrade from SUSE Storage v1.8.x to SUSE Storage v1.9.3, please refer to the Migration section.

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

Migration

To migrate SUSE Storage to SUSE Storage, please refer to the procedures described in the Migrating to SUSE Storage documentation.

Post-release known issues

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

Resolved issues

Improvement

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

  • #12034 [BACKPORT][v1.9.3][IMPROVEMENT] improve error logging for failed mounting during node publish volume

  • #12122 [BACKPORT][v1.9.3][IMPROVEMENT] The auto-delete-pod-when-volume-detached-unexpectedly should only focus on the kuberentes builtin workload.

  • #11947 [BACKPORT][v1.9.3][IMPROVEMENT] Avoid repeat engine restart when there are replica unavailable during migration

  • #11748 [BACKPORT][v1.9.3][IMPROVEMENT] Collect Logs from the Host Directory Defined by the Setting log-path

Bug

  • #12090 [BACKPORT][v1.9.3][BUG] Backup target metric is broken

  • #12116 [BACKPORT][v1.9.3][BUG] Replicas accumulate during engine upgrade

  • #11956 [BACKPORT][v1.9.3][BUG] RWX volume causes process uninterruptible sleep

  • #11720 [BACKPORT][v1.9.3][BUG] Backing image download gets stuck after network disconnection

  • #11556 [BACKPORT][v1.9.3][BUG] Test case test_recurring_jobs_when_volume_detached_unexpectedly failed: backup completed but progress did not reach 100%

  • #11974 [BACKPORT][v1.9.3][BUG] Fix SPDK v25.05 CVE issue

  • #12087 [BACKPORT][v1.9.3][BUG] panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 at longhorn-engine/pkg/controller/control.go:218 +0x2de]

  • #12063 [BACKPORT][v1.9.3][BUG] Unable to complete uninstallation due to the remaining backuptarget

  • #11927 [BACKPORT][v1.9.3][BUG] NPE error during recurring job execution

  • #11999 [BACKPORT][v1.9.3][BUG] DR volume gets stuck in unknown state if engine image is deleted from the attached node

  • #11997 [BACKPORT][v1.9.3][BUG] Volume gets stuck in attaching state if engine image is not deployed on one of nodes

  • #11900 [BACKPORT][v1.9.3][BUG] longhorn-engine’s UI panics

  • #11896 [BACKPORT][v1.9.3][BUG] Volume is unable to upgrade if the number of active replicas is larger than volumme.spec.numberOfReplicas

  • #11573 [BACKPORT][v1.9.3][BUG] SUSE Storage fails to create Backing Image Backup on ARM platform