SPDK v25.05 の CVE 問題の修正
原文を表示
- [BACKPORT][v1.10.1][BUG] Fix SPDK v25.05 CVE issue [11970](https://github.com/longhorn/longhorn/issues/11970) - @derekbit @roger-ryaogithub.com/longhorn/longhorn/releases/tag/v1.10.1
週次メールは確認すべき変更がある週だけ、深刻度がcriticalのセキュリティアドバイザリは即時に届きます。
この緩和策では、アップグレード時のバージョンチェックを無効化し、manager イメージのタグを v1.10.1 から v1.10.1-hotfix-2 に変更します。
> To mitigate the issues, replace `longhorn-manager:v1.10.1` with the hotfixed image `longhorn-manager:v1.10.1-hotfix-2`. > Follow these steps to apply the update: > 1. **Disable the upgrade version check** > - Helm users: Set `upgradeVersionCheck` to `false` in the `values.yaml` file. > - Manifest users: Remove the `--upgrade-version-check` flag from the deployment manifest. > 2. **Update the `longhorn-manager` image** > - Change the image tag from `v1.10.1` to `v1.10.1-hotfix-2` in the appropriate file: > - For Helm: Update `values.yaml` > - For manifests: Update the deployment manifest directly. > 3. **Proceed with the upgrade** > - Apply the changes using your standard Helm upgrade command or reapply the updated manifest.github.com/longhorn/longhorn/releases/tag/v1.10.1
etcd または CRD の復元により、v1beta1 のデータが残ることがあります。アップグレード前に、CR を手動で v1beta2 に移行し、CRD の保存済みバージョンに v1beta1 が含まれていないことを確認するよう推奨されています。
> If your Longhorn cluster was initially deployed with a version earlier than v1.3.0, the Custom Resources (CRs) were created using the `v1beta1` APIs. While the upgrade from Longhorn v1.8 to v1.9 automatically migrates all CRs to the new `v1beta2` version, **a manual CR migration is strongly advised before upgrading from Longhorn `v1.9` to `v1.10`**. > Certain operations, such as an `etcd` or CRD restore, may leave behind `v1beta1` data. Manually migrating your CRs ensures that all Longhorn data is properly updated to the `v1beta2` API, preventing potential compatibility issues and unexpected behavior with the new Longhorn version. > Following the manual migration, **verify that `v1beta1` has been removed from the CRD stored versions** to ensure completion and a successful upgrade. > For more details, see [Kubernetes official document for CRD storage version](https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning/#upgrade-existing-objects-to-a-new-stored-version), and [Issue #11886](https://github.com/longhorn/longhorn/issues/11886).github.com/longhorn/longhorn/releases/tag/v1.10.1
この移行では、まず settings-CR の UPDATE 検証を一時的に無効にし、storedVersions に v1beta1 を含む CRD に注釈を付けます。次に、該当する CRD の storedVersions を v1beta2 に変更し、その後、検証を再び有効にします。コマンドでは longhorn-system を使用します。カスタム名前空間を使用するインストールでは、代わりにその名前空間を使用してください。
> #### Migration Requirement Before Longhorn v1.10 Upgrade
>
> Before upgrading from Longhorn v1.9 to v1.10, perform the following manual CRD storage version migration.
>
> > **Note**: If your Longhorn installation uses a namespace other than `longhorn-system`, replace `longhorn-system` with your custom namespace throughout the commands.
>
> ```bash
> # Temporarily disable the CR validation webhook to allow updating read-only settings CRs.
> kubectl patch validatingwebhookconfiguration longhorn-webhook-validator \
> --type=merge \
> -p "$(kubectl get validatingwebhookconfiguration longhorn-webhook-validator -o json | \
> jq '.webhooks[0].rules |= map(if .apiGroups == ["longhorn.io"] and .resources == ["settings"] then
> .operations |= map(select(. != "UPDATE")) else . end)')"
>
> # Migrate CRDs that ever stored v1beta1 resources
> migration_time="$(date +%Y-%m-%dT%H:%M:%S)"
> crds=($(kubectl get crd -l app.kubernetes.io/name=longhorn -o json | jq -r '.items[] | select(.status.storedVersions | index("v1beta1")) | .metadata.name'))
> for crd in "${crds[@]}"; do
> echo "Migrating ${crd} ..."
> for name in $(kubectl -n longhorn-system get "$crd" -o jsonpath='{.items[*].metadata.name}'); do
> # Attach additional annotations to trigger v1beta1 resource updating in the latest storage version.
> kubectl patch "${crd}" "${name}" -n longhorn-system --type=merge -p='{"metadata":{"annotations":{"migration-time":"'"${migration_time}"'"}}}'
> done
> # Clean up the stored version in CRD status
> kubectl patch crd "${crd}" --type=merge -p '{"status":{"storedVersions":["v1beta2"]}}' --subresource=status
> done
>
> # Re-enable the CR validation webhook.
> kubectl patch validatingwebhookconfiguration longhorn-webhook-validator \
> --type=merge \
> -p "$(kubectl get validatingwebhookconfiguration longhorn-webhook-validator -o json | \
> jq '.webhooks[0].rules |= map(if .apiGroups == ["longhorn.io"] and .resources == ["settings"] then
> .operations |= (. + ["UPDATE"] | unique) else . end)')"
> ```github.com/longhorn/longhorn/releases/tag/v1.10.1移行スクリプトの実行後、すべての Longhorn CRD の storedVersions には v1beta2 だけが記載され、v1beta1 は含まれていない必要があります。その後、v1.10 へのアップグレードは問題なく進められるとリリースノートに記載されています。
> After running the script, verify the CRD stored versions using this command:
>
> ```bash
> kubectl get crd -l app.kubernetes.io/name=longhorn -o=jsonpath='{range .items[*]}{.metadata.name}{": "}{.status.storedVersions}{"\n"}{end}'
> ```
> Crucially, all Longhorn CRDs MUST have only `"v1beta2"` listed in `storedVersions` (i.e., `"v1beta1"` must be completely absent) before proceeding to the v1.10 upgrade.
> Example of successful output:
> ```
> backingimagedatasources.longhorn.io: ["v1beta2"]
> backingimagemanagers.longhorn.io: ["v1beta2"]
> backingimages.longhorn.io: ["v1beta2"]
> backupbackingimages.longhorn.io: ["v1beta2"]
> backups.longhorn.io: ["v1beta2"]
> backuptargets.longhorn.io: ["v1beta2"]
> backupvolumes.longhorn.io: ["v1beta2"]
> engineimages.longhorn.io: ["v1beta2"]
> engines.longhorn.io: ["v1beta2"]
> instancemanagers.longhorn.io: ["v1beta2"]
> nodes.longhorn.io: ["v1beta2"]
> orphans.longhorn.io: ["v1beta2"]
> recurringjobs.longhorn.io: ["v1beta2"]
> replicas.longhorn.io: ["v1beta2"]
> settings.longhorn.io: ["v1beta2"]
> sharemanagers.longhorn.io: ["v1beta2"]
> snapshots.longhorn.io: ["v1beta2"]
> supportbundles.longhorn.io: ["v1beta2"]
> systembackups.longhorn.io: ["v1beta2"]
> systemrestores.longhorn.io: ["v1beta2"]
> volumeattachments.longhorn.io: ["v1beta2"]
> volumes.longhorn.io: ["v1beta2"]
> ```
> With these steps completed, the Longhorn upgrade to v1.10 should now proceed without issues.github.com/longhorn/longhorn/releases/tag/v1.10.1必須のアップグレード前移行が適用されておらず、CR がすべて v1beta2 に移行されていない場合、longhorn-manager Pod が正常に動作しないことがあります。よくあるパッチエラーは、status.storedVersions に v1beta1 が残っていることを示しています。
> If you did not apply the required pre-upgrade migration steps and the CRs are not fully migrated to `v1beta2`, the `longhorn-manager` Pods may fail to operate correctly. A common error message for this issue is: > > ``` > Upgrade failed: cannot patch "backingimagedatasources.longhorn.io" with kind CustomResourceDefinition: CustomResourceDefinition.apiextensions.k8s.io "backingimagedatasources.longhorn.io" is invalid: status.storedVersions[0]: Invalid value: "v1beta1": missing from spec.versions; v1beta1 was previously a storage version, and must remain in spec.versions until a storage migration ensures no data remains persisted in v1beta1 and removes v1beta1 from status.storedVersions > ```github.com/longhorn/longhorn/releases/tag/v1.10.1
v1beta1 CR の移行Longhorn が v1.9.x で安定した後、移行が必要です。
> ##### Post-Downgrade > Once the downgrade is complete and the Longhorn system is stable on the v1.9.x version, you must immediately follow the steps outlined in the **Migration Requirement Before Longhorn v1.10 Upgrade**. This step is crucial to migrate all remaining `v1beta1` CRs to `v1beta2` before attempting the Longhorn v1.10 upgrade again.github.com/longhorn/longhorn/releases/tag/v1.10.1
> [!IMPORTANT] **Ensure that your cluster is running Kubernetes v1.25 or later before installing Longhorn v1.10.1.**github.com/longhorn/longhorn/releases/tag/v1.10.1
> [!IMPORTANT] **Ensure that your cluster is running Kubernetes v1.25 or later before upgrading from Longhorn v1.9.x to v1.10.1.**github.com/longhorn/longhorn/releases/tag/v1.10.1
Longhorn only allows upgrades from supported versions. For more information about upgrade paths and procedures, see [Upgrade](https://longhorn.io/docs/1.10.0/deploy/upgrade/) in the Longhorn documentation.github.com/longhorn/longhorn/releases/tag/v1.10.1
> The `longhorn-manager:v1.10.1` image is affected bygithub.com/longhorn/longhorn/releases/tag/v1.10.1
特定の条件下で、manager が nil ポインター参照を起こし、予期せずクラッシュすることがあります。
> - Regression: > - [\[BUG\] invalid memory address or nil pointer dereference](https://github.com/longhorn/longhorn/issues/12233) that can trigger a nil-pointer dereference under certain conditions, potentially causing unexpected crashes.github.com/longhorn/longhorn/releases/tag/v1.10.1
新しい移行エンジンが実行状態へ遷移できず、VM の移行が停止したままになることがあります。
> - [\[BUG\] Block Mode Volume Migration Stuck](https://github.com/longhorn/longhorn/issues/12311) that can cause block mode volume migration to get stuck indefinitely.github.com/longhorn/longhorn/releases/tag/v1.10.1
クローン処理中に、VolumeAttachment の検証 webhook が一部の CSI PublishVolume リクエストを拒否します。これにより、一時ボリュームのアタッチが数分遅れます。
> - Day-one issues: > - V2 volume clone: > - [\[BUG\] V2 Volume CSI Clone Slowness Caused by VolumeAttachment Webhook](https://github.com/longhorn/longhorn/issues/12328) that can lead to significant delays during V2 volume cloning operations.github.com/longhorn/longhorn/releases/tag/v1.10.1
> - [\[BUG\] [Bug] A cloned volume cannot be attached to a workload](https://github.com/longhorn/longhorn/issues/12206) that prevents cloned volumes from being attached to workloads.github.com/longhorn/longhorn/releases/tag/v1.10.1
ディスク逼迫時、停止中ボリュームの PVC ID が稼働中ボリュームの PVC ID より先にソートされると、稼働中ボリュームの自動バランス調整が行われない場合があります。
> - Replica auto-balance: > - [\[BUG\] Replica auto balance disk pressure threshold stalled with stopped volumes](https://github.com/longhorn/longhorn/issues/10837) that can cause the replica auto-balance feature to stall when volumes are stopped under disk pressure conditions.github.com/longhorn/longhorn/releases/tag/v1.10.1
longhorn-manager:v1.10.1 の既知の問題このイメージには、nilポインター参照によるクラッシュ、ブロックモードのボリューム移行の停止、V2 ボリュームのクローン作成の遅延、クローン作成したボリュームをワークロードにアタッチできない問題、ディスク圧迫時に停止中のボリュームがあるとレプリカの自動バランス調整が停止する問題があります。緩和策として、longhorn-manager:v1.10.1-hotfix-2 が記載されています。
> The `longhorn-manager:v1.10.1` image is affected by > - Regression: > - [\[BUG\] invalid memory address or nil pointer dereference](https://github.com/longhorn/longhorn/issues/12233) that can trigger a nil-pointer dereference under certain conditions, potentially causing unexpected crashes. > - [\[BUG\] Block Mode Volume Migration Stuck](https://github.com/longhorn/longhorn/issues/12311) that can cause block mode volume migration to get stuck indefinitely. > - Day-one issues: > - V2 volume clone: > - [\[BUG\] V2 Volume CSI Clone Slowness Caused by VolumeAttachment Webhook](https://github.com/longhorn/longhorn/issues/12328) that can lead to significant delays during V2 volume cloning operations. > - [\[BUG\] [Bug] A cloned volume cannot be attached to a workload](https://github.com/longhorn/longhorn/issues/12206) that prevents cloned volumes from being attached to workloads. > - Replica auto-balance: > - [\[BUG\] Replica auto balance disk pressure threshold stalled with stopped volumes](https://github.com/longhorn/longhorn/issues/10837) that can cause the replica auto-balance feature to stall when volumes are stopped under disk pressure conditions. > To mitigate the issues, replace `longhorn-manager:v1.10.1` with the hotfixed image `longhorn-manager:v1.10.1-hotfix-2`. > Follow these steps to apply the update: > 1. **Disable the upgrade version check** > - Helm users: Set `upgradeVersionCheck` to `false` in the `values.yaml` file. > - Manifest users: Remove the `--upgrade-version-check` flag from the deployment manifest. > > 2. **Update the `longhorn-manager` image** > - Change the image tag from `v1.10.1` to `v1.10.1-hotfix-2` in the appropriate file: > - For Helm: Update `values.yaml` > - For manifests: Update the deployment manifest directly. > > 3. **Proceed with the upgrade** > - Apply the changes using your standard Helm upgrade command or reapply the updated manifest.github.com/longhorn/longhorn/releases/tag/v1.10.1
kubectl を使用してインストールした環境では、ダウングレードの前に current-longhorn-version を元のバージョンにパッチしてください。
> To fix this issue, you must perform a **forced downgrade** back to the **exact Longhorn v1.9.x version** that was running before the failed upgrade attempt.
> ##### Downgrade Procedure (kubectl Installation)
> If Longhorn was installed using `kubectl`, you must patch the `current-longhorn-version` setting before downgrading. Replace `v1.9.x` with the original version before upgrade in the following commands.
>
> ```bash
> # Attaching annotation to allow patching current-longhorn-version.
> kubectl patch settings.longhorn.io current-longhorn-version -n longhorn-system --type=merge -p='{"metadata":{"annotations":{"longhorn.io/update-setting-from-longhorn":""}}}'
> # Temporarily override current version to allow old version installation
> # Replace the value `"v1.9.x" to the original version before upgrade.
> kubectl patch settings.longhorn.io current-longhorn-version -n longhorn-system --type=merge -p='{"value":"v1.9.x"}'
> ```
> After modifying `current-longhorn-version`, you can proceed to downgrade to the original Longhorn v1.9.x deployment.github.com/longhorn/longhorn/releases/tag/v1.10.1- [BACKPORT][v1.10.1][BUG] Fix SPDK v25.05 CVE issue [11970](https://github.com/longhorn/longhorn/issues/11970) - @derekbit @roger-ryaogithub.com/longhorn/longhorn/releases/tag/v1.10.1
- [BACKPORT][v1.10.1][BUG] Backup target metric is broken [12089](https://github.com/longhorn/longhorn/issues/12089) - @mantissahz @roger-ryaogithub.com/longhorn/longhorn/releases/tag/v1.10.1
ブロックディスクの削除を試みた際に、この問題が発生することがありました。
- [BACKPORT][v1.10.1][BUG] Block disk deletion fails without error message [11954](https://github.com/longhorn/longhorn/issues/11954) - @davidcheng0922 @roger-ryaogithub.com/longhorn/longhorn/releases/tag/v1.10.1
dataEngine 未設定時に CSIStorageCapacity の作成が通知なく失敗する問題の修正表面化しなかった不具合dataEngine なしで csi-provisioner を実行している環境この修正以前は、dataEngine が未設定の場合、csi-provisioner は CSIStorageCapacity の作成に失敗しても、そのことを通知しませんでした。
- [BACKPORT][v1.10.1][BUG] csi-provisioner silently fails to create CSIStorageCapacity if dataEngine parameter is missing [11918](https://github.com/longhorn/longhorn/issues/11918) - @yangchiu @bachmanity1github.com/longhorn/longhorn/releases/tag/v1.10.1
このリークにより、時間の経過とともにメモリ使用量が増加し、安定性の問題が発生する可能性がありました。
### Goroutine Leak in Instance Manager (V2 Data Engine) Fixed a goroutine leak in the instance manager when using the V2 data engine. This issue could lead to increased memory usage and potential stability problems over time. For more details, see [Issue #11962](https://github.com/longhorn/longhorn/issues/11962). - [BACKPORT][v1.10.1][BUG] Goroutine leak in instance-manager when using v2 data engine [11962](https://github.com/longhorn/longhorn/issues/11962) - @PhanLe1010 @chriscchiengithub.com/longhorn/longhorn/releases/tag/v1.10.1
v1.10.0 では割り込みモードが AIO ディスクのみをサポートしていたため、NVMe ディスクでこのモードを使用する V2 ボリュームが、アタッチ中のまま無期限に進まなくなることがありました。NVMe ディスクの割り込みモードは v1.10.1 以降でサポートされます。
### V2 Volume Attachment Failure in Interrupt Mode Fixed an issue where V2 volumes using interrupt mode with NVMe disks could fail to complete the attachment process, causing volumes to remain stuck in the attaching state indefinitely. In Longhorn v1.10.0, interrupt mode supports only **AIO disks**. Interrupt mode for **NVMe disks** is supported starting in v1.10.1. For more details, see [Issue #11816](https://github.com/longhorn/longhorn/issues/11816).github.com/longhorn/longhorn/releases/tag/v1.10.1
v1.10.0 では、これらのノードへの UI のデプロイに失敗していました。IPv6 を必要とせず、IPv4 のみの構成に対応するようになりました。
### UI Deployment Failure on IPv4-Only Nodes Fixed a bug introduced in v1.10.0 where the Longhorn UI failed to deploy on nodes with only IPv4 enabled. The UI now correctly supports IPv4-only configurations without requiring IPv6. For more details, see [Issue #11875](https://github.com/longhorn/longhorn/issues/11875). - [BACKPORT][v1.10.1][BUG] UI fails to deploy when only IPv4 is enabled on nodes with v1.10.0 version [11875](https://github.com/longhorn/longhorn/issues/11875) - @yangchiu @c3y1huanggithub.com/longhorn/longhorn/releases/tag/v1.10.1
共有マネージャーは、これらのボリュームで過剰なメモリーを消費していました。通常の運用では、メモリー使用量が安定するようになりました。
### Share Manager Excessive Memory Usage Fixed excessive memory consumption in the share manager for RWX (ReadWriteMany) volumes. The component now maintains stable memory usage under normal operation. For more details, see [Issue #12043](https://github.com/longhorn/longhorn/issues/12043). - [BACKPORT][v1.10.1][BUG] share-manager excessive memory usage [12043](https://github.com/longhorn/longhorn/issues/12043) - @derekbit @chriscchiengithub.com/longhorn/longhorn/releases/tag/v1.10.1
ダウンロード中にネットワークが切断されると、バッキングイメージのダウンロードが停止したままになることがありました。
- [BACKPORT][v1.10.1][BUG] Backing image download gets stuck after network disconnection [12094](https://github.com/longhorn/longhorn/issues/12094) - @COLDTURNIP @chriscchiengithub.com/longhorn/longhorn/releases/tag/v1.10.1
エンジンで、longhorn-engine/pkg/controller/control.go:218 において、無効なメモリアドレスまたは nil ポインターの逆参照による SIGSEGV が発生し、パニックになる可能性がありました。
- [BACKPORT][v1.10.1][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 [12088](https://github.com/longhorn/longhorn/issues/12088) - @roger-ryaogithub.com/longhorn/longhorn/releases/tag/v1.10.1
v2 データエンジンで、BDF で指定された NVME ディスクを検出できない場合がありました。
- [BACKPORT][v1.10.1][BUG] NVME disk not found in v2 data engine (failed to find device for BDF) [12029](https://github.com/longhorn/longhorn/issues/12029) - @derekbit @roger-ryaogithub.com/longhorn/longhorn/releases/tag/v1.10.1
定期ジョブの実行中に nil ポインターエラーが発生することがありました。リリースノートには、発生条件は記載されていません。
- [BACKPORT][v1.10.1][BUG] NPE error during recurring job execution [11926](https://github.com/longhorn/longhorn/issues/11926) - @yangchiu @shuo-wugithub.com/longhorn/longhorn/releases/tag/v1.10.1
このリリースより前は、Talos ノードで v2 ボリュームを作成すると失敗することがありました。
- [BACKPORT][v1.10.1][BUG] v2 volume creation failed on talos nodes [12026](https://github.com/longhorn/longhorn/issues/12026) - @c3y1huang @chriscchiengithub.com/longhorn/longhorn/releases/tag/v1.10.1
unknown のままになる問題の修正アタッチ先のノードからエンジンイメージが削除されると、ボリュームが unknown のままになることがありました。
- [BACKPORT][v1.10.1][BUG] DR volume gets stuck in `unknown` state if engine image is deleted from the attached node [11998](https://github.com/longhorn/longhorn/issues/11998) - @yangchiu @shuo-wugithub.com/longhorn/longhorn/releases/tag/v1.10.1
attaching 状態で停止する問題の修正エンジンイメージが関連するノードのいずれかにデプロイされていない場合、ボリュームが attaching のまま停止することがありました。
- [BACKPORT][v1.10.1][BUG] Volume gets stuck in `attaching` state if engine image image is not deployed on one of nodes [11996](https://github.com/longhorn/longhorn/issues/11996) - @yangchiu @shuo-wugithub.com/longhorn/longhorn/releases/tag/v1.10.1
V2 割り込みモードを使用すると、V2 ボリュームの接続処理が停止したままになることがありました。
- [BACKPORT][v1.10.1][BUG] V2 volume stuck in volume attachment (V2 interrupt mode) [11976](https://github.com/longhorn/longhorn/issues/11976) - @c3y1huang @chriscchiengithub.com/longhorn/longhorn/releases/tag/v1.10.1
このリリース以前は、RWX ボリュームを使用するプロセスが割り込み不能なスリープ状態に入ることがありました。
- [BACKPORT][v1.10.1][BUG] RWX volume causes process uninterruptible sleep [11958](https://github.com/longhorn/longhorn/issues/11958) - @COLDTURNIP @chriscchiengithub.com/longhorn/longhorn/releases/tag/v1.10.1
longhorn-manager 起動失敗の修正Longhorn 1.9.2 から 1.10.0 にアップグレードした後、longhorn-manager が起動しないことがありました。
- [BACKPORT][v1.10.1][BUG] longhorn-manager fails to start after upgrading from 1.9.2 to 1.10.0 [11865](https://github.com/longhorn/longhorn/issues/11865) - @derekbit @roger-ryaogithub.com/longhorn/longhorn/releases/tag/v1.10.1
リリースノートには、影響を受ける操作、問題の発生条件、具体的な修正内容が記載されていません。
- [BACKPORT][v1.10.1][BUG] invalid memory address or nil pointer dereference [11942](https://github.com/longhorn/longhorn/issues/11942) - @bachmanity1 @roger-ryaogithub.com/longhorn/longhorn/releases/tag/v1.10.1
UI がパニックを起こす可能性がありましたが、リリースノートには、引き金となる操作や条件は記載されていません。
- [BACKPORT][v1.10.1][BUG] longhorn-engine's UI panics [11901](https://github.com/longhorn/longhorn/issues/11901) - @derekbit @chriscchiengithub.com/longhorn/longhorn/releases/tag/v1.10.1
v1.10.0 へのアップグレード後、新しい Pod のデプロイに失敗することがありました。この回帰を緩和するため、v1.10.1 のリリース前にホットフィックスイメージが作成されました。
- [HOTFIX] Create hotfixed image for longhorn-manager:v1.10.0 [11951](https://github.com/longhorn/longhorn/issues/11951) - @c3y1huang @roger-ryaogithub.com/longhorn/longhorn/releases/tag/v1.10.1
- [BACKPORT][v1.10.1][IMPROVEMENT] The `auto-delete-pod-when-volume-detached-unexpectedly` should only focus on the kubernetes builtin workload. [12125](https://github.com/longhorn/longhorn/issues/12125) - @derekbit @chriscchiengithub.com/longhorn/longhorn/releases/tag/v1.10.1
CSIStorageCapacity オブジェクトでの割り当て可能容量の報告- [BACKPORT][v1.10.1][IMPROVEMENT] `CSIStorageCapacity` objects must show schedulable (allocatable) capacity [12036](https://github.com/longhorn/longhorn/issues/12036) - @chriscchien @bachmanity1github.com/longhorn/longhorn/releases/tag/v1.10.1
- [BACKPORT][v1.10.1][IMPROVEMENT] improve error logging for failed mounting during node publish volume [12033](https://github.com/longhorn/longhorn/issues/12033) - @COLDTURNIP @roger-ryaogithub.com/longhorn/longhorn/releases/tag/v1.10.1
defaultSettings の自動引用符付与と複数型への対応- [BACKPORT][v1.10.1][IMPROVEMENT] Improve Helm Chart defaultSettings handling with automatic quoting and multi-type support [12020](https://github.com/longhorn/longhorn/issues/12020) - @derekbit @chriscchiengithub.com/longhorn/longhorn/releases/tag/v1.10.1
- [BACKPORT][v1.10.1][IMPROVEMENT] Avoid repeat engine restart when there are replica unavailable during migration [11945](https://github.com/longhorn/longhorn/issues/11945) - @yangchiu @shuo-wugithub.com/longhorn/longhorn/releases/tag/v1.10.1
GuaranteedInstanceManagerCPU の上限引き上げ- [BACKPORT][v1.10.1][IMPROVEMENT] Adjust maximum of GuaranteedInstanceManagerCPU to a big value [11968](https://github.com/longhorn/longhorn/issues/11968) - @mantissahzgithub.com/longhorn/longhorn/releases/tag/v1.10.1
- [BACKPORT][v1.10.1][IMPROVEMENT] Add usage metrics for Longhorn installation variant [11795](https://github.com/longhorn/longhorn/issues/11795) - @derekbitgithub.com/longhorn/longhorn/releases/tag/v1.10.1
backuptarget によるアンインストール阻害の修正- [BACKPORT][v1.10.1][BUG] Unable to complete uninstallation due to the remaining backuptarget [11964](https://github.com/longhorn/longhorn/issues/11964) - @mantissahz @roger-ryaogithub.com/longhorn/longhorn/releases/tag/v1.10.1
- [BACKPORT][v1.10.1][BUG] mounting error is not properly hanedled during CSI node publish volume [12008](https://github.com/longhorn/longhorn/issues/12008) - @COLDTURNIPgithub.com/longhorn/longhorn/releases/tag/v1.10.1
- [BACKPORT][v1.10.1][BUG] Adding multiple disks to the same node concurrently may occasionally fail [12018](https://github.com/longhorn/longhorn/issues/12018) - @davidcheng0922 @roger-ryaogithub.com/longhorn/longhorn/releases/tag/v1.10.1
- [BUG] upgrading from 1.9.1 to 1.10.0 fails due to old resources still being in v1beta1 [11886](https://github.com/longhorn/longhorn/issues/11886) - @COLDTURNIP @roger-ryaogithub.com/longhorn/longhorn/releases/tag/v1.10.1
- [BACKPORT][v1.10.1][BUG] Unable to re-add block-type disks by BDF after re-enable v2 data engine [12000](https://github.com/longhorn/longhorn/issues/12000) - @yangchiu @davidcheng0922github.com/longhorn/longhorn/releases/tag/v1.10.1
- [BACKPORT][v1.10.1][BUG] `test_system_backup_and_restore` test case failed on master-head [12005](https://github.com/longhorn/longhorn/issues/12005) - @derekbit @chriscchiengithub.com/longhorn/longhorn/releases/tag/v1.10.1
- [BACKPORT][v1.10.1][BUG] Volume is unable to upgrade if the number of active replicas is larger than `volumme.spec.numberOfReplicas` [11895](https://github.com/longhorn/longhorn/issues/11895) - @yangchiu @derekbitgithub.com/longhorn/longhorn/releases/tag/v1.10.1
- [BACKPORT][v1.10.1][BUG] Unable to detach a v2 volume after labeling `disable-v2-data-engine=true` [11801](https://github.com/longhorn/longhorn/issues/11801) - @mantissahzgithub.com/longhorn/longhorn/releases/tag/v1.10.1
- [BACKPORT][v1.10.1][REFACTOR] SAST checks for UI component [11992](https://github.com/longhorn/longhorn/issues/11992) - @chriscchiengithub.com/longhorn/longhorn/releases/tag/v1.10.1
整理した内容は AI が作成するため誤っている可能性があり、無保証で提供されます。