Skip to content

Releases: rancher/suse-storage

SUSE Storage v1.10.3

10 May 23:25
@derekbit derekbit
v1.10.3
4f39430

Choose a tag to compare

View all tags
SUSE Storage v1.10.3

SUSE Storage v1.10.3 Release Notes

SUSE Storage v1.10.3 introduces several improvements and bug fixes that are intended to improve system quality, resilience, stability and security.

The SUSE Storage team appreciates your contributions and expects to receive feedback regarding this release.

Note

For more information about release-related terminology, see Releases.

Installation

Important

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

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

Upgrade

Important

Ensure that your cluster is running Kubernetes v1.25 or later before upgrading from SUSE Storage v1.10.x (< v1.10.3) to v1.10.3. To upgrade from Longhorn v1.9.x to SUSE Storage v1.10.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 SUSE Storage documentation.

Migration

To migrate Longhorn 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.

Post-Release Known Issues

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

Resolved Issues

Improvement

  • [BACKPORT][v1.10.3][IMPROVEMENT] Relax endpoint-network-for-rwx-volume validation for migratable block-mode volumes 12712 - @c3y1huang @chriscchien

Bug

  • [BACKPORT][v1.10.3][BUG] Backup to S3 fails at 95% 12715 - @yangchiu @mantissahz
  • [BACKPORT][v1.10.3][BUG] orphan controller does not cleanup the instance on the corresponding instance manager on a multiple IM node 12787 - @COLDTURNIP @roger-ryao
  • [BACKPORT][v1.10.3][BUG] Replica Auto-Balance Causes Infinite Replica Scheduling Loop 12931 - @yangchiu @shuo-wu
  • [BACKPORT][v1.10.3][BUG] Node exhaustion caused by backup inspect buildup induced due to NFS latency 12946 - @COLDTURNIP @roger-ryao
  • [BACKPORT][v1.10.3][BUG] "snapshot becomes not ready to use" Warning events emitted during expected auto-cleanup after backup 12857 - @yangchiu
  • [BACKPORT][v1.10.3][BUG] Potential NEP in Volume Metrics Collector 12734 - @derekbit @chriscchien
  • [BACKPORT][v1.10.3][BUG] Backing image data source pod fails when HTTP proxy is enabled 12781 - @c3y1huang @chriscchien
  • [BACKPORT][v1.10.3][BUG] V2 Volume Clone Status is Changed Over Time 12747 - @davidcheng0922 @roger-ryao
  • [BACKPORT][v1.10.3][BUG] Google Cloud Storage (GCS) backup target always fails with SignatureDoesNotMatch due to AWS SDK Go v2 CRC32 checksum incompatibility 12716 - @mantissahz @chriscchien
  • [BACKPORT][v1.10.3][BUG] Incorrect storage double-counting causes scheduling failure when multiple replicas exist on the same node 12662 - @yangchiu @davidcheng0922
  • [BACKPORT][v1.10.3][BUG] Longhorn v1.10 Volume API is not compatible with the v1.8.1 manifest 12617 - @mantissahz @roger-ryao
  • [BACKPORT][v1.10.3][BUG] Volume.Spec.CloneMode is empty after upgrading to v1.10.x and following version 12616 - @mantissahz

Contributors

Contributors

COLDTURNIP, innobead, and 13 other contributors
Loading

SUSE Storage v1.9.5

07 May 07:50
@derekbit derekbit
v1.9.5
e68c5d4

Choose a tag to compare

View all tags
SUSE Storage v1.9.5

SUSE Storage v1.9.5 Release Notes

SUSE Storage 1.9.5 introduces several improvements and bug fixes that are intended to improve system quality, resilience, stability and security.

The SUSE Storage team appreciates your contributions and expects to receive feedback regarding this release.

Note

For more information about release-related terminology, see Releases.

Installation

Important

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

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

Upgrade

Important

Ensure that your cluster is running Kubernetes v1.25 or later before upgrading from SUSE Storage v1.9.x (< v1.9.5) to v1.9.5. To upgrade from Longhorn v1.8.x to SUSE Storage v1.9.5, 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 SUSE Storage documentation.

Migration

To migrate Longhorn 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.

Post-Release Known Issues

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

Resolved Issues

Bug

  • [BACKPORT][v1.9.5][BUG] orphan controller does not cleanup the instance on the corresponding instance manager on a multiple IM node 12789 - @COLDTURNIP @roger-ryao
  • [BACKPORT][v1.9.5][BUG] Backing image data source pod fails when HTTP proxy is enabled 12784 - @c3y1huang @chriscchien

Contributors

Contributors

COLDTURNIP, innobead, and 9 other contributors
Loading

SUSE Storage v1.11.2

18 May 01:02
@derekbit derekbit
v1.11.2
666fcb2

Choose a tag to compare

View all tags
SUSE Storage v1.11.2 Latest
Latest

SUSE Storage v1.11.2 Release Notes

SUSE Storage v1.11.2 is a patch release that focuses on critical bug fixes, security hardening, and stability improvements for both V1 and V2 data engines. Key highlights include a fix for a significant memory leak in the instance manager and improvements to backup reliability and volume scheduling.

We welcome feedback and contributions to help continuously improve SUSE Storage.

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

Installation

Important

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

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

Upgrade

Important

Ensure that your cluster is running Kubernetes v1.25 or later before upgrading from SUSE Storage v1.10.x to v1.11.2. To upgrade from Longhorn v1.10.x to SUSE Storage v1.11.2, 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 SUSE Storage documentation.

Migration

To migrate Longhorn 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 in this release

Bug

  • [BACKPORT][v1.11.2][BUG] Test case test_storage_capacity_aware_pod_scheduling fails 13006 - @yangchiu @bachmanity1
  • [BACKPORT][v1.11.2][BUG] Replica Auto-Balance Causes Infinite Replica Scheduling Loop 12928 - @yangchiu @shuo-wu
  • [BACKPORT][v1.11.2][BUG] CSIStorageCapacity reports 0 for compute nodes without Longhorn disks, breaking WaitForFirstConsumer scheduling 12918 - @chriscchien @bachmanity1
  • [BACKPORT][v1.11.2][BUG] Replica rebuild progress can go over 100% 12952 - @yangchiu @davidcheng0922
  • [BACKPORT][v1.11.2][BUG] Node exhaustion caused by backup inspect buildup induced due to NFS latency 12945 - @COLDTURNIP @roger-ryao
  • [BACKPORT][v1.11.2][BUG] Backup engine SIGSEGV on aarch64 with 16K page size kernel (Fedora Asahi Remix / Apple Silicon) — v1.11.1 12930 - @mantissahz
  • [BACKPORT][v1.11.2][BUG] Failed to collect health data for block disk (AIO) when disk path is a /dev/disk/by-id symlink 12911 - @yangchiu @hookak
  • [BACKPORT][v1.11.2][BUG] "snapshot becomes not ready to use" Warning events emitted during expected auto-cleanup after backup 12856 - @yangchiu

Misc

Contributors

Contributors

COLDTURNIP, innobead, and 14 other contributors
Assets 3
Loading

SUSE Storage v1.11.1

16 Mar 14:16
@derekbit derekbit
v1.11.1
eb37902

Choose a tag to compare

View all tags
SUSE Storage v1.11.1

SUSE Storage v1.11.1 Release Notes

SUSE Storage v1.11.1 is a patch release that focuses on critical bug fixes, security hardening, and stability improvements for both V1 and V2 data engines. Key highlights include a fix for a significant memory leak in the instance manager and improvements to backup reliability and volume scheduling.

We welcome feedback and contributions to help continuously improve SUSE Storage.

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

Important Fixes

This release includes several critical stability fixes.

Longhorn 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 & 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 some 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

Important

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 Rancher, Kubectl, and Helm. For more information about installation methods and requirements, see Installation in the SUSE Storage documentation.

Upgrade

Important

Ensure that your cluster is running Kubernetes v1.25 or later before upgrading from SUSE Storage v1.10.x to v1.11.1. To upgrade from Longhorn v1.10.x to SUSE Storage v1.11.1, 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 SUSE Storage documentation.

Migration

To migrate Longhorn 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 in this release

Improvement

  • [BACKPORT][v1.11.1][IMPROVEMENT] Ensure V2 Engine ReplicaAdd respects the fast-replica-rebuild-enabled setting 12751 - @davidcheng0922 @roger-ryao
  • [BACKPORT][v1.11.1][IMPROVEMENT] Topology-aware PV nodeAffinity control: allowedTopologies keys + strictTopology 12689 - @hookak @roger-ryao
  • [BACKPORT][v1.11.1][IMPROVEMENT] detailed log for the reason of node controller deleting backing image copies 12585 - @COLDTURNIP @yangchiu
  • [BACKPORT][v1.11.1][IMPROVEMENT] Relax endpoint-network-for-rwx-volume validation for migratable block-mode volumes 12711 - @c3y1huang @chriscchien
  • [BACKPORT][v1.11.1][IMPROVEMENT] RBAC permissions for csi-resizer 12694 - @yangchiu

Bug

  • [BACKPORT][v1.11.1][BUG] Failed replicas accumulate during engine upgrade 12768 - @davidcheng0922
  • [BACKPORT][v1.11.1][BUG] V2 Volume Clone Status is Changed Over Time 12748 - @davidcheng0922 @roger-ryao
  • [BACKPORT][v1.11.1][BUG] Backup to S3 fails at 95% 12714 - @yangchiu @mantissahz
  • [BACKPORT][v1.11.1][BUG] spdk_tgt encountered an assertion failure in longhorn-spdk-helper during a CI test run 12738 - @derekbit @roger-ryao
  • [BACKPORT][v1.11.1][BUG] Google Cloud Storage (GCS) backup target always fails with SignatureDoesNotMatch due to AWS SDK Go v2 CRC32 checksum incompatibility 12688 - @mantissahz @chriscchien
  • [BACKPORT][v1.11.1][BUG] Enable to set defaultSettings.nodeDiskHealthMonitoring 12730 - @chriscchien
  • [BACKPORT][v1.11.1][BUG] stale name variable in nsmounter get_pid 12704 - @chriscchien
  • [BACKPORT][v1.11.1][BUG] After upgrading to 1.11.0, new persistent volumes have nodeAffinity 12665 - @chriscchien
  • [BACKPORT][v1.11.1][BUG] Incorrect storage double-counting causes scheduling failure when multiple replicas exist on the same node 12661 - @yangchiu @davidcheng0922
  • [BACKPORT][v1.11.1][BUG] Recreated block disk with same name never becomes schedulable after volume and disk deletion 12641 - @davidcheng0922
  • [BACKPORT][v1.11.1][BUG] Longhorn v1.10 Volume API is not compatible with the v1.8.1 manifest 12618 - @mantissahz @roger-ryao
  • [BACKPORT][v1.11.1][BUG] [v2] Can't use partition as block device 12626 - @bachmanity1
  • [BACKPORT][v1.11.1][BUG] Volume.Spec.CloneMode is empty after upgrading to v1.10.x and following version 12615 - @mantissahz
  • [BACKPORT][v1.11.1][BUG] Longhorn validating webhook blocks k3s server node joins - flannel CNI fails to initialize 12589 - @yangchiu @mantissahz
  • [BACKPORT][v1.11.1][BUG] V1.11.0 very high memory consumption for instance manager 12575 - @derekbit @roger-ryao
  • [BACKPORT][v1.11.1][BUG] Backing image data source pod fails when HTTP proxy is enabled 12780 - @c3y1huang @chriscchien
  • [BACKPORT][v1.11.1][BUG] orphan controller does not cleanup the instance on the corresponding instance manager on a multiple IM node 12788 - @COLDTURNIP @roger-ryao

Stability

Contributors

Contributors

COLDTURNIP, innobead, and 15 other contributors
Loading

SUSE Storage v1.10.2

29 Jan 08:58
@derekbit derekbit
v1.10.2
c8648f5

Choose a tag to compare

View all tags
SUSE Storage v1.10.2

SUSE Storage v1.10.2 Release Notes

SUSE Storage 1.10.2 introduces several improvements and bug fixes that are intended to improve system quality, resilience, stability and security.

We welcome feedback and contributions to help continuously improve SUSE Storage.

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 Issue #12231.

Encrypted Volume Cannot Be Expanded Online

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

For more details, see Issue #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 Issue #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 Issue #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 Issue #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 Issue #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 Issue #12200 and Issue #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 Issue #12251.

Installation

Important

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 Rancher, Kubectl, and Helm. For more information about installation methods and requirements, see Installation in the SUSE Storage documentation.

Upgrade

Important

Ensure that your cluster is running Kubernetes v1.25 or later before upgrading from SUSE Storage v1.9.x to v1.10.2. To upgrade from Longhorn v1.9.x to SUSE Storage v1.10.2, 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 SUSE Storage documentation.

Migration

To migrate Longhorn 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

Feature

  • [BACKPORT][v1.10.2][FEATURE] Inherit namespace for longhorn-share-manager in FastFailover mode 12245 - @yangchiu
  • [BACKPORT][v1.10.2][FEATURE] [Dependency] aws-sdk-go v1.55.7 is EOL as of 2025-07-31 — plan to migrate to v2? 12181 - @mantissahz @roger-ryao

Improvement

  • [BACKPORT][v1.10.2][IMPROVEMENT] Fix V2 Volume CSI Clone Slowness Caused by VolumeAttachment Webhook Blocking 12329 - @PhanLe1010 @roger-ryao

Bug

Contributors

Contributors

COLDTURNIP, innobead, and 14 other contributors
Loading

SUSE Storage v1.9.4

19 Dec 15:07
@derekbit derekbit
v1.9.4
2a2b7d2

Choose a tag to compare

View all tags
SUSE Storage v1.9.4

SUSE Storage 1.9.4 introduces several improvements and bug fixes that are intended to improve system quality, resilience, stability and security.

The SUSE Storage team appreciates your contributions and expects to receive feedback regarding this release.

Note

For more information about release-related terminology, see Releases.

Installation

Important

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

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

Upgrade

Important

Ensure that your cluster is running Kubernetes v1.25 or later before upgrading from SUSE Storage v1.9.x (< v1.9.4) to v1.9.4. To upgrade from Longhorn v1.8.x to SUSE Storage v1.9.4, 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 SUSE Storage documentation.

Migration

To migrate Longhorn 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.

Post-Release Known Issues

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

Resolved Issues

Bug

Contributors

Contributors

COLDTURNIP, innobead, and 11 other contributors
Loading

Suse Storage v1.9.4-rc2

18 Dec 07:04
@derekbit derekbit
v1.9.4-rc2
e0caa86

Choose a tag to compare

View all tags
Suse Storage v1.9.4-rc2 Pre-release
Pre-release

DON'T UPGRADE from/to any RC/Preview/Sprint releases because the operation is not supported.

Resolved Issues in this release

Bug

Contributors

Contributors

COLDTURNIP, yangchiu, and 4 other contributors
Loading

Suse Storage v1.9.4-rc1

17 Dec 03:59
@derekbit derekbit
v1.9.4-rc1
c227bd6

Choose a tag to compare

View all tags
Suse Storage v1.9.4-rc1 Pre-release
Pre-release

DON'T UPGRADE from/to any RC/Preview/Sprint releases because the operation is not supported.

Resolved Issues in this release

Bug

Contributors

Contributors

COLDTURNIP, yangchiu, and 4 other contributors
Loading

SUSE Storage v1.9.3

18 Nov 07:34
@derekbit derekbit
v1.9.3
eaf6afb

Choose a tag to compare

View all tags
SUSE Storage v1.9.3

SUSE Storage 1.9.3 introduces several improvements and bug fixes that are intended to improve system quality, resilience, stability and security.

The SUSE Storage team appreciates your contributions and expects to receive feedback regarding this release.

Note

For more information about release-related terminology, see Releases.

Installation

Important

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 Rancher, Kubectl, and Helm. For more information about installation methods and requirements, see Installation in the SUSE Storage documentation.

Upgrade

Important

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 Longhorn 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 SUSE Storage documentation.

Migration

To migrate Longhorn 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.

Post-Release Known Issues

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

Resolved Issues

Improvement

  • [BACKPORT][v1.9.3][FEATURE] [Dependency] aws-sdk-go v1.55.7 is EOL as of 2025-07-31 — plan to migrate to v2? 12182 - @mantissahz @roger-ryao
  • [BACKPORT][v1.9.3][IMPROVEMENT] improve error logging for failed mounting during node publish volume 12034 - @COLDTURNIP @yangchiu
  • [BACKPORT][v1.9.3][IMPROVEMENT] The auto-delete-pod-when-volume-detached-unexpectedly should only focus on the kuberentes builtin workload. 12122 - @derekbit
  • [BACKPORT][v1.9.3][IMPROVEMENT] Avoid repeat engine restart when there are replica unavailable during migration 11947 - @yangchiu @shuo-wu
  • [BACKPORT][v1.9.3][IMPROVEMENT] Collect Logs from the Host Directory Defined by the Setting log-path 11748 - @c3y1huang @roger-ryao

Bug

  • [BACKPORT][v1.9.3][BUG] Backup target metric is broken 12090 - @mantissahz @roger-ryao
  • [BACKPORT][v1.9.3][BUG] Replicas accumulate during engine upgrade 12116 - @c3y1huang @chriscchien
  • [BACKPORT][v1.9.3][BUG] RWX volume causes process uninterruptable sleep 11956 - @COLDTURNIP @chriscchien
  • [BACKPORT][v1.9.3][BUG] Backing image download gets stuck after network disconnection 11720 - @COLDTURNIP @chriscchien
  • [BACKPORT][v1.9.3][BUG] Test case test_recurring_jobs_when_volume_detached_unexpectedly failed: backup completed but progress did not reach 100% 11556 - @yangchiu @mantissahz
  • [BACKPORT][v1.9.3][BUG] Fix SPDK v25.05 CVE issue 11974 - @derekbit @roger-ryao
  • [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 12087 - @roger-ryao
  • [BACKPORT][v1.9.3][BUG] Unable to complete uninstallation due to the remaining backuptarget 12063 - @mantissahz @roger-ryao
  • [BACKPORT][v1.9.3][BUG] NPE error during recurring job execution 11927 - @yangchiu @shuo-wu
  • [BACKPORT][v1.9.3][BUG] DR volume gets stuck in unknown state if engine image is deleted from the attached node 11999 - @yangchiu @shuo-wu
  • [BACKPORT][v1.9.3][BUG] Volume gets stuck in attaching state if engine image image is not deployed on one of nodes 11997 - @yangchiu @shuo-wu
  • [BACKPORT][v1.9.3][BUG] longhorn-engine's UI panics 11900 - @derekbit @chriscchien
  • [BACKPORT][v1.9.3][BUG] Volume is unable to upgrade if the number of active replicas is larger than volumme.spec.numberOfReplicas 11896 - @yangchiu @derekbit
  • [BACKPORT][v1.9.3][BUG] Longhorn fails to create Backing Image Backup on ARM platform 11573 - @COLDTURNIP

Contributors

Contributors

COLDTURNIP, innobead, and 12 other contributors
Loading

Suse Storage v1.9.3-rc1

17 Nov 09:48
@derekbit derekbit
v1.9.3-rc1
e18a695

Choose a tag to compare

View all tags
Suse Storage v1.9.3-rc1 Pre-release
Pre-release

DON'T UPGRADE from/to any RC/Preview/Sprint releases because the operation is not supported.

Resolved Issues in this release

Feature

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

Improvement

  • [BACKPORT][v1.9.3][IMPROVEMENT] improve error logging for failed mounting during node publish volume 12034 - @COLDTURNIP @yangchiu
  • [BACKPORT][v1.9.3][IMPROVEMENT] The auto-delete-pod-when-volume-detached-unexpectedly should only focus on the kuberentes builtin workload. 12122 - @derekbit
  • [BACKPORT][v1.9.3][IMPROVEMENT] Avoid repeat engine restart when there are replica unavailable during migration 11947 - @yangchiu @shuo-wu
  • [BACKPORT][v1.9.3][IMPROVEMENT] Collect Logs from the Host Directory Defined by the Setting log-path 11748 - @c3y1huang @roger-ryao

Bug

  • [BACKPORT][v1.9.3][BUG] Backup target metric is broken 12090 - @mantissahz @roger-ryao
  • [BACKPORT][v1.9.3][BUG] Replicas accumulate during engine upgrade 12116 - @c3y1huang @chriscchien
  • [BACKPORT][v1.9.3][BUG] RWX volume causes process uninterruptable sleep 11956 - @COLDTURNIP @chriscchien
  • [BACKPORT][v1.9.3][BUG] Backing image download gets stuck after network disconnection 11720 - @COLDTURNIP @chriscchien
  • [BACKPORT][v1.9.3][BUG] Test case test_recurring_jobs_when_volume_detached_unexpectedly failed: backup completed but progress did not reach 100% 11556 - @yangchiu @mantissahz
  • [BACKPORT][v1.9.3][BUG] Fix SPDK v25.05 CVE issue 11974 - @derekbit @roger-ryao
  • [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 12087 - @roger-ryao
  • [BACKPORT][v1.9.3][BUG] Unable to complete uninstallation due to the remaining backuptarget 12063 - @mantissahz @roger-ryao
  • [BACKPORT][v1.9.3][BUG] NPE error during recurring job execution 11927 - @yangchiu @shuo-wu
  • [BACKPORT][v1.9.3][BUG] DR volume gets stuck in unknown state if engine image is deleted from the attached node 11999 - @yangchiu @shuo-wu
  • [BACKPORT][v1.9.3][BUG] Volume gets stuck in attaching state if engine image image is not deployed on one of nodes 11997 - @yangchiu @shuo-wu
  • [BACKPORT][v1.9.3][BUG] longhorn-engine's UI panics 11900 - @derekbit @chriscchien
  • [BACKPORT][v1.9.3][BUG] Volume is unable to upgrade if the number of active replicas is larger than volumme.spec.numberOfReplicas 11896 - @yangchiu @derekbit
  • [BACKPORT][v1.9.3][BUG] Longhorn fails to create Backing Image Backup on ARM platform 11573 - @COLDTURNIP

Contributors

Contributors

COLDTURNIP, yangchiu, and 6 other contributors
Loading