SUSE Storage v1.10.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.10.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.10.x (< v1.10.3) to v1.10.3. To upgrade from SUSE Storage 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 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

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

Bug

  • #12715 [BACKPORT][v1.10.3][BUG] Backup to S3 fails at 95%

  • #12787 [BACKPORT][v1.10.3][BUG] Orphan controller does not cleanup the instance on the corresponding instance manager on a multiple IM node

  • #12931 [BACKPORT][v1.10.3][BUG] Replica Auto-Balance Causes Infinite Replica Scheduling Loop

  • #12946 [BACKPORT][v1.10.3][BUG] Node exhaustion caused by backup inspect buildup induced due to NFS latency

  • #12857 [BACKPORT][v1.10.3][BUG] "snapshot becomes not ready to use" Warning events emitted during expected auto-cleanup after backup

  • #12734 [BACKPORT][v1.10.3][BUG] Potential NEP in Volume Metrics Collector

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

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

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

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

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

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