SUSE Storage v1.9.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 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.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.8.x or v1.9.x (< v1.9.2) to v1.9.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

Improvement

  • #11805 [BACKPORT][v1.9.2][IMPROVEMENT] Add usage metrics for Longhorn installation variant

  • #11782 [BACKPORT][v1.9.2][IMPROVEMENT] SAST Potential dereference of the null pointer in controller/volume_controller.go in longhorn-manager

  • #11726 [BACKPORT][v1.9.2][IMPROVEMENT] Collect mount table, process status and process table in support bundle

  • #11567 [BACKPORT][v1.9.2][IMPROVEMENT] rename the backing image manager to reduce the probability of CR name collision

  • #11604 [BACKPORT][v1.9.2][IMPROVEMENT] Improve log messages of longhorn-engine, tgt and liblonghorn for troubleshooting

  • #11501 [BACKPORT][v1.9.2][IMPROVEMENT] Misleading log message Deleting orphans on evicted node …​

  • #11324 [BACKPORT][v1.9.2][IMPROVEMENT] Check if the backup target is available before creating a backup, backup backing image, and system backup

  • #11310 [BACKPORT][v1.9.2][IMPROVEMENT] adjust the hardcoded timeout limitation for backing image downloading

  • #11508 [BACKPORT][v1.9.2][IMPROVEMENT] Improve longhorn-engine controller log messages

  • #11506 [BACKPORT][v1.9.2][IMPROVEMENT] Make liveness probe parameters of instance-manager pod configurable

  • #11488 [BACKPORT][v1.9.2][IMPROVEMENT] backing image handle node disk deleting events

  • #11327 [BACKPORT][v1.9.2][IMPROVEMENT] Handle credential secret containing mixed invalid conditions

  • #11193 [BACKPORT][v1.9.2][IMPROVEMENT] Improve the condition message of engine image check

Bug

  • #11788 [BACKPORT][v1.9.2][BUG] Potential Data Corruption During Volume Resizing When Created from Snapshot

  • #11744 [BUG] [v1.9.x] support bundle stuck at 33%

  • #11639 [BACKPORT][v1.9.2][BUG] Unable to disable v2-data-engine even though there is no V2 volumes, backing images or orphaned data

  • #11722 [BACKPORT][v1.9.2][BUG] SUSE Storage pvcs are in pending state.

  • #11729 [BUG] Broken link in documentation

  • #11710 [BACKPORT][v1.9.2][BUG] longhornctl preflight install should load and check iscsi_tcp kernel module.

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

  • #11341 [BACKPORT][v1.9.2][BUG] Volume becomes faulted when its replica node disks run out of space during a write operation

  • #11606 [BACKPORT][v1.9.2][BUG] Engine process continues running after rapid volume detachment

  • #11648 [BACKPORT][v1.9.2][BUG] Creating a 2 Gi volume with a 200 Mi backing image is rejected with “volume size should be larger than the backing image size”

  • #11599 [BACKPORT][v1.9.2][BUG] longhorn-manager repeatedly emits No instance manager for node xxx for update instance state of orphan instance orphan-xxx..

  • #11692 [BACKPORT][v1.9.2][BUG] BackupBackingImage may be created from an unready BackingImageManager

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

  • #11614 [BACKPORT][v1.9.2][BUG] remaining unknown OS condition in node CR

  • #11584 [BACKPORT][v1.9.2][BUG] Volumes fails to remount when they go read-only

  • #11590 [BACKPORT][v1.9.2][BUG] Dangling Volume State When Live Migration Terminates Unexpectedly

  • #11482 [BACKPORT][v1.9.2][BUG] Unable to setup backup target in storage network environment: cannot find a running instance manager for node

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

  • #11494 [BACKPORT][v1.9.2][BUG] Recurring Job with 'default' group causes goroutine deadlock on v1.9.1 (Regression of #11020)

  • #11391 [BACKPORT][v1.9.2][BUG] Test Case test_replica_auto_balance_node_least_effort Is Sometimes Failed

  • #11344 [BACKPORT][v1.9.2][BUG] Unable to set up S3 backup target if backups already exist

  • #11422 [BACKPORT][v1.9.2][BUG] longhorn-manager is crashed due to SIGSEGV: segmentation violation

  • #11382 [BACKPORT][v1.9.2][BUG] Typo in configuration parameter: "offlineRelicaRebuilding" should be "offlineReplicaRebuilding"

  • #11841 [BUG][UI][v1.9.2-rc2] Unable to Retrieve Volume’s Backup List in the Operation