SPDK v25.05 CVE issue fixed
Show release-note lines
- [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
Email is sent weekly only when there are changes to check; critical security advisories are sent immediately.
The mitigation disables the upgrade version check and changes the manager image tag from v1.10.1 to 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
An etcd or CRD restore may leave v1beta1 data behind. The note recommends manually migrating CRs to v1beta2 and confirming v1beta1 is absent from CRD stored versions before upgrading.
> 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
The migration temporarily disables settings-CR UPDATE validation, annotates CRDs whose storedVersions include v1beta1, changes those CRDs' storedVersions to v1beta2, then re-enables validation. The commands use longhorn-system; installations with a custom namespace use that namespace instead.
> #### 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.1After running the migration script, every Longhorn CRD must list only v1beta2 in storedVersions, with v1beta1 absent. The note says the v1.10 upgrade should then proceed without issues.
> 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.1If the required pre-upgrade migration has not been applied and CRs are not fully migrated to v1beta2, longhorn-manager Pods may fail to operate correctly. A common patch error indicates v1beta1 remains in status.storedVersions.
> 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 migration before retrying the v1.10 upgradeThe migration is required once Longhorn is stable on 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
Under certain conditions, the manager can hit a nil-pointer dereference and crash unexpectedly.
> - 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
The new migration engine can fail to transition to running, leaving VM migration stuck.
> - [\[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
During the clone workflow, the VolumeAttachment validator webhook rejects some CSI PublishVolume requests. This delays temporary-volume attachment by several minutes.
> - 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
Under disk pressure, running volumes may not be auto-balanced when stopped-volume PVC IDs sort before the running volumes’ PVC IDs.
> - 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.1The image is affected by a nil-pointer-dereference crash, stuck block-mode volume migration, slow V2 volume cloning, cloned volumes that cannot attach to workloads, and stalled replica auto-balance with stopped volumes under disk pressure. The note lists longhorn-manager:v1.10.1-hotfix-2 as the mitigation.
> 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
For installations installed using kubectl, patch current-longhorn-version to the original version before downgrading.
> 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
This could happen when block disk deletion was attempted.
- [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
CSIStorageCapacity creation failure with missing dataEngine fixedSilent failurecsi-provisioner without dataEngineBefore this fix, csi-provisioner silently failed to create CSIStorageCapacity when dataEngine was missing.
- [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
The leak could increase memory use and cause stability problems over time.
### 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
In v1.10.0, interrupt mode supported only AIO disks, so V2 volumes using it with NVMe disks could remain stuck in the attaching state indefinitely. Interrupt mode for NVMe disks is supported starting in 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
In v1.10.0, the UI failed to deploy on these nodes. It now supports IPv4-only configurations without requiring IPv6.
### 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
The share manager consumed excessive memory for these volumes. Under normal operation, it now maintains stable memory usage.
### 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
A backing image download could get stuck after a network disconnection during the download.
- [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
The engine could panic with an invalid-memory-address or nil-pointer-dereference SIGSEGV at longhorn-engine/pkg/controller/control.go:218.
- [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
The v2 data engine could fail to find an NVME disk addressed by BDF.
- [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
A nil-pointer error could occur during recurring job execution; the note does not identify the conditions that triggered it.
- [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
Before this release, creating v2 volumes on Talos nodes could fail.
- [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 after engine image deletion fixedIf the engine image was deleted from the node to which it was attached, the volume could remain stuck in 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 fixedA volume could remain stuck in attaching when the engine image was not deployed on one of its nodes.
- [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
A V2 volume could become stuck during attachment when V2 interrupt mode was used.
- [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
Before this release, a process using an RWX volume could enter uninterruptible sleep.
- [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 startup failure after upgradesAfter upgrading from 1.9.2 to 1.10.0, longhorn-manager could fail to start.
- [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
The release note does not identify the affected operation, what triggered the problem, or the exact correction.
- [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
The UI could panic, but the note does not identify the operation or conditions that triggered it.
- [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
After upgrading to v1.10.0, new pods could fail to deploy. A hotfix image was created before v1.10.1 to mitigate the regression.
- [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 objects report allocatable capacity- [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 fixed- [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 resources resolved- [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
Summaries are produced by AI, so they can be wrong, and they are provided without warranty.