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
확인할 변경이 있을 때만 주 1회, critical 보안 공지는 즉시 발송
이 완화 조치는 업그레이드 버전 검사를 비활성화하고 매니저 이미지 태그를 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
특정 조건에서 Longhorn 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
새 마이그레이션 엔진이 running 상태로 전환되지 못해 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 검증 웹훅이 일부 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의 알려진 문제이 이미지에는 널 포인터 역참조로 인한 크래시, 블록 모드 볼륨 마이그레이션 중단, 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 볼륨이 연결 중 상태에서 무기한 멈춰 있을 수 있었습니다. v1.10.1부터 NVMe 디스크의 인터럽트 모드를 지원합니다.
### 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
Recurring Job 실행 중 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 상태에 멈추는 DR 볼륨 문제 수정볼륨이 연결된 노드에서 엔진 이미지가 삭제되면 볼륨이 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 시작 실패 수정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
v1beta1 리소스로 발생한 실패 해결- [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가 작성하므로 틀릴 수 있으며, 보증 없이 제공합니다.