RATATOSKRATATOSK
ログイン

Longhorn

v1.10.2Storage & Data
2026年1月28日

CHECK 2OTHER 23

v1.10.2には、使用するイメージやノード構成に応じて適用範囲が分かれる変更が含まれています。特定の環境では、イメージの更新やクラスタDNSへの問い合わせに関する修正が関係します。

影響確認 (2)

  • securityinstance-manager によるクラスタDNSへの過剰なTXTクエリの修正

    instance-manager がハードディスクまたはソリッドステートディスクのないノードで動作する場合に適用されます。

    ハードディスクまたはソリッドステートディスクのないノードで動作する instance-manager が、クラスタのDNSサーバーに _grpc_config.localhost へのTXTクエリを大量に送信する不具合が修正されました。

  • breakingbacking-image-manager のホットフィックス版への置き換え

    backing-image-manager:v1.10.2 を使うデプロイメントに適用されます。

    backing-image-manager:v1.10.2 を、ホットフィックス版の backing-image-manager:v1.10.2-hotfix-1 に置き換える変更です。

その他の記録済み変更 23 件すべてfixes 22 · additions 1

fixes (22)

  • Fixed a race condition where **ReadWriteMany (RWX) volumes** could remain in the *attaching* state after node drains, causing workloads to become unavailable.
  • Fixed an issue where online expansion of encrypted volumes did not propagate the new size to the dm-crypt device.
  • Fixed a bug where cloned volumes could fail to reach a healthy state, preventing attachment to workloads.
  • 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.
  • Fixed an issue where replica auto-balance under disk pressure could be blocked if stopped volumes were present on the disk.
  • Fixed a bug where temporary replicas could accumulate during engine upgrade.
  • Fixed potential context leaks in the instance manager client and backing image manager client, improving stability and preventing resource exhaustion.
  • 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.
  • [BACKPORT][v1.10.2][IMPROVEMENT] Fix V2 Volume CSI Clone Slowness Caused by VolumeAttachment Webhook Blocking
  • Replica rebuild, clone and restore fail, traffic being sent to HTTP proxy
  • Healthy replica could be deleted unexpectedly after reducing volume's number of replicas
  • Data locality enabled volume fails to remove an existing running replica after numberOfReplicas reduced
  • System backup may fail to be created or deleted
  • Some default settings in questions.yaml are placed incorrectly.
  • Auto balance feature may lead to volumes falling into a replica deletion-recreation loop
  • Single replica volume could get stuck in attaching/detaching loop after the replica node rebooted
  • SnapshotBack proxy request might be sent to incorrect instance-manager pod
  • unknown OS condition in node CR is not properly removed during upgrade
  • mounting error is not properly hanedled during CSI node publish volume
  • The auo generated backing image pod name is complained by kubelet
  • invalid memory address or nil pointer dereference (again)
  • Request Header Or Cookie Too Large in Web UI with OIDC auth

additions (1)

  • [BACKPORT][v1.10.2][FEATURE] Inherit namespace for longhorn-share-manager in FastFailover mode
Longhornをスタックに追加

対応が必要なリリースが出たときに、週次メールでお知らせします。 今回のセキュリティパッチと破壊的変更も、その一例です。

スタックに追加