Skip to content

Releases: longhorn/longhorn

Longhorn v1.10.0-rc2

11 Sep 09:14
@derekbit derekbit
v1.10.0-rc2
b9fa597
Compare
Choose a tag to compare
Longhorn v1.10.0-rc2 Pre-release
Pre-release

DON'T UPGRADE from/to any RC/Preview/Sprint releases because the operation is not supported.

Resolved Issues in this release

Highlight

Feature

Improvement

Read more

Contributors

COLDTURNIP, innobead, and 28 other contributors
Loading

Longhorn v1.9.2-rc1

11 Sep 12:30
@derekbit derekbit
v1.9.2-rc1
93ca281
Compare
Choose a tag to compare
Longhorn v1.9.2-rc1 Pre-release
Pre-release

DON'T UPGRADE from/to any RC/Preview/Sprint releases because the operation is not supported.

Resolved Issues in this release

Improvement

  • [BACKPORT][v1.9.2][IMPROVEMENT] Collect mount table, process status and process table in support bundle 11726 - @mantissahz @chriscchien
  • [BACKPORT][v1.9.2][IMPROVEMENT] rename the backing image manager to reduce the probability of CR name collision 11567 - @COLDTURNIP @chriscchien
  • [BACKPORT][v1.9.2][IMPROVEMENT] Improve log messages of longhorn-engine, tgt and liblonghorn for troubleshooting 11604 - @yangchiu @derekbit
  • [BACKPORT][v1.9.2][IMPROVEMENT] Misleading log message Deleting orphans on evicted node ... 11501 - @yangchiu @derekbit
  • [BACKPORT][v1.9.2][IMPROVEMENT] Check if the backup target is available before creating a backup, backup backing image, and system backup 11324 - @yangchiu @nzhan126
  • [BACKPORT][v1.9.2][IMPROVEMENT] adjust the hardcoded timeout limitation for backing image downloading 11310 - @COLDTURNIP @chriscchien
  • [BACKPORT][v1.9.2][IMPROVEMENT] Improve longhorn-engine controller log messages 11508 - @derekbit @chriscchien
  • [BACKPORT][v1.9.2][IMPROVEMENT] Make liveness probe parameters of instance-manager pod configurable 11506 - @derekbit @chriscchien
  • [BACKPORT][v1.9.2][IMPROVEMENT] backing image handle node disk deleting events 11488 - @COLDTURNIP @chriscchien
  • [BACKPORT][v1.9.2][IMPROVEMENT] Handle credential secret containing mixed invalid conditions 11327 - @yangchiu @nzhan126
  • [BACKPORT][v1.9.2][IMPROVEMENT] Improve the condition message of engine image check 11193 - @derekbit @chriscchien

Bug

  • [BUG] [v1.9.x] support bundle stuck at 33% 11744 - @mantissahz @chriscchien
  • [BACKPORT][v1.9.2][BUG] Unable to disable v2-data-engine even though there is no v2 volumes, backing images or orphaned data 11639 - @shuo-wu @chriscchien
  • [BACKPORT][v1.9.2][BUG] Longhorn pvcs are in pending state. 11722 - @yangchiu @derekbit
  • [BUG] Broken link in documentation 11729 - @consideRatio
  • [BACKPORT][v1.9.2][BUG] longhornctl preflight install should load and chec iscsi_tcp kernel module. 11710 - @mantissahz @chriscchien
  • [BACKPORT][v1.9.2][BUG] Backing image download gets stuck after network disconnection 11624 - @COLDTURNIP
  • [BACKPORT][v1.9.2][BUG] Volume becomes faulted when its replica node disks run out of space during a write operation 11341 - @mantissahz @chriscchien
  • [BACKPORT][v1.9.2][BUG] Engine process continues running after rapid volume detachment 11606 - @COLDTURNIP @yangchiu @chriscchien
  • [BACKPORT][v1.9.2][BUG] Creating a 2 Gi volume with a 200 Mi backing image is rejected with “volume size should be larger than the backing image size” 11648 - @COLDTURNIP @yangchiu @chriscchien
  • [BACKPORT][v1.9.2][BUG] longhorn-manager repeatedly emits No instance manager for node xxx for update instance state of orphan instance orphan-xxx.. 11599 - @COLDTURNIP @chriscchien
  • [BACKPORT][v1.9.2][BUG] BackupBackingImage may be created from an unready BackingImageManager 11692 - @WebberHuang1118 @roger-ryao
  • [BACKPORT][v1.9.2][BUG] Longhorn fails to create Backing Image Backup on ARM platform 11570 - @COLDTURNIP
  • [BACKPORT][v1.9.2][BUG] remaining unknown OS condition in node CR 11614 - @COLDTURNIP @roger-ryao
  • [BACKPORT][v1.9.2][BUG] Volumes fails to remount when they go read-only 11584 - @derekbit @chriscchien
  • [BACKPORT][v1.9.2][BUG] Dangling Volume State When Live Migration Terminates Unexpectedly 11590 - @PhanLe1010 @chriscchien
  • [BACKPORT][v1.9.2][BUG] Unable to setup backup target in storage network environment: cannot find a running instance manager for node 11482 - @derekbit @chriscchien
  • [BACKPORT][v1.9.2][BUG] Test case test_recurring_jobs_when_volume_detached_unexpectedly failed: backup completed but progress did not reach 100% 11476 - @yangchiu @mantissahz
  • [BACKPORT][v1.9.2][BUG] Recurring Job with 'default' group causes goroutine deadlock on v1.9.1 (Regression of #11020) 11494 - @c3y1huang
  • [BACKPORT][v1.9.2][BUG] Test Case test_replica_auto_balance_node_least_effort Is Sometimes Failed 11391 - @derekbit @chriscchien
  • [BACKPORT][v1.9.2][BUG] Unable to set up S3 backup target if backups already exist 11344 - @mantissahz @chriscchien
  • [BACKPORT][v1.9.2][BUG] longhorn-manager is crashed due to SIGSEGV: segmentation violation 11422 - @derekbit @roger-ryao
  • [BACKPORT][v1.9.2][BUG] Typo in configuration parameter: "offlineRelicaRebuilding" should be "offlineReplicaRebuilding" 11382 - @yangchiu

Contributors

Contributors

COLDTURNIP, innobead, and 11 other contributors
Loading

Longhorn v1.10.0-rc1

03 Sep 12:02
@derekbit derekbit
v1.10.0-rc1
48bb04f
Compare
Choose a tag to compare
Longhorn v1.10.0-rc1 Pre-release
Pre-release

DON'T UPGRADE from/to any RC/Preview/Sprint releases because the operation is not supported.

Resolved Issues in this release

Highlight

Feature

Improvement

Read more

Contributors

COLDTURNIP, innobead, and 27 other contributors
Loading

Longhorn v1.9.1

23 Jul 07:57
@derekbit derekbit
v1.9.1
a9e986b
Compare
Choose a tag to compare
Longhorn v1.9.1 Latest
Latest

Longhorn v1.9.1 Release Notes

Longhorn 1.9.1 introduces several improvements and bug fixes that are intended to improve system quality, resilience, stability and security.

The Longhorn team appreciates your contributions and expects to receive feedback regarding this release.

Note

For more information about release-related terminology, see Releases.

Installation

Important

Ensure that your cluster is running Kubernetes v1.25 or later before installing Longhorn v1.9.1.

You can install Longhorn using a variety of tools, including Rancher, Kubectl, and Helm. For more information about installation methods and requirements, see Quick Installation in the Longhorn documentation.

Upgrade

Important

Ensure that your cluster is running Kubernetes v1.25 or later before upgrading from Longhorn v1.8.x or v1.9.x (< v1.9.1) to v1.9.1.

Longhorn only allows upgrades from supported versions. For more information about upgrade paths and procedures, see Upgrade in the Longhorn documentation.

Post-Release Known Issues

For information about issues identified after this release, see Release-Known-Issues.

Resolved Issues

Feature

Improvement

  • [BACKPORT][v1.9.1][IMPROVEMENT] Remove the Patch preserveUnknownFields: false for CRDs 11280 - @derekbit @chriscchien
  • [BACKPORT][v1.9.1][IMPROVEMENT] Improve the disk space un-schedulable condition message 11212 - @yangchiu @davidcheng0922
  • [BACKPORT][v1.9.1][IMPROVEMENT] Improve the condition message of engine image check 11196 - @derekbit @chriscchien
  • [BACKPORT][v1.9.1][IMPROVEMENT] Improve the logging when detecting multiple backup volumes of the same volume on the same backup target 11225 - @PhanLe1010 @chriscchien
  • [BACKPORT][v1.9.1][IMPROVEMENT] extra invalid BackupVolumeCR may be created during cluster split-brain 11168 - @mantissahz @roger-ryao
  • [BACKPORT][v1.9.1][IMPROVEMENT] Full replica rebuilding when a node goes down for a while and then comes back 11069 - @mantissahz
  • [BACKPORT][v1.9.1][IMPROVEMENT] Adding retry logic for longhorn-csi-plugin when it trying to contact the longhorn-manager pods 10914 - @PhanLe1010 @roger-ryao

Bug

Misc

New Contributors

Contributors

Contributors

COLDTURNIP, innobead, and 16 other contributors
Assets 6
Loading

Longhorn v1.9.1-rc1

16 Jul 08:39
@derekbit derekbit
v1.9.1-rc1
e1a89e6
Compare
Choose a tag to compare
Longhorn v1.9.1-rc1 Pre-release
Pre-release

DON'T UPGRADE from/to any RC/Preview/Sprint releases because the operation is not supported.

Resolved Issues in this release

Feature

Improvement

  • [BACKPORT][v1.9.1][IMPROVEMENT] Remove the Patch preserveUnknownFields: false for CRDs 11280 - @derekbit @chriscchien
  • [BACKPORT][v1.9.1][IMPROVEMENT] Improve the disk space un-schedulable condition message 11212 - @yangchiu @davidcheng0922
  • [BACKPORT][v1.9.1][IMPROVEMENT] Improve the condition message of engine image check 11196 - @derekbit @chriscchien
  • [BACKPORT][v1.9.1][IMPROVEMENT] Improve the logging when detecting multiple backup volumes of the same volume on the same backup target 11225 - @PhanLe1010 @chriscchien
  • [BACKPORT][v1.9.1][IMPROVEMENT] extra invalid BackupVolumeCR may be created during cluster split-brain 11168 - @mantissahz @roger-ryao
  • [BACKPORT][v1.9.1][IMPROVEMENT] Full replica rebuilding when a node goes down for a while and then comes back 11069 - @mantissahz
  • [BACKPORT][v1.9.1][IMPROVEMENT] Adding retry logic for longhorn-csi-plugin when it trying to contact the longhorn-manager pods 10914 - @PhanLe1010 @roger-ryao

Bug

Misc

Contributors

Contributors

COLDTURNIP, innobead, and 12 other contributors
Loading

Longhorn v1.8.2

09 Jun 05:40
@derekbit derekbit
v1.8.2
93fe371
Compare
Choose a tag to compare
Longhorn v1.8.2

Longhorn v1.8.2 Release Notes

Longhorn 1.8.2 introduces several improvements and bug fixes that are intended to improve system quality, resilience, stability and security.

The Longhorn team appreciates your contributions and expects to receive feedback regarding this release.

Note

For more information about release-related terminology, see Releases.

Installation

Important

Ensure that your cluster is running Kubernetes v1.25 or later before installing Longhorn v1.8.2.

You can install Longhorn using a variety of tools, including Rancher, Kubectl, and Helm. For more information about installation methods and requirements, see Quick Installation in the Longhorn documentation.

Upgrade

Important

Ensure that your cluster is running Kubernetes v1.25 or later before upgrading from Longhorn v1.7.x or v1.8.x (< v1.8.2) to v1.8.2.

Longhorn only allows upgrades from supported versions. For more information about upgrade paths and procedures, see Upgrade in the Longhorn documentation.

Post-Release Known Issues

For information about issues identified after this release, see Release-Known-Issues.

Resolved Issues

Improvement

  • [BACKPORT][v1.8.2][IMPROVEMENT] Adding retry logic for longhorn-csi-plugin when it is trying to contact the longhorn-manager pods 11027 - @PhanLe1010 @roger-ryao
  • [BACKPORT][v1.8.2][IMPROVEMENT] add strict field validation to the update option in upgrade path 10648 - @ChanYiLin
  • [BACKPORT][v1.8.2][IMPROVEMENT] Move SettingNameV2DataEngineHugepageLimit to danger zone settings 10568 - @derekbit @chriscchien
  • [BACKPORT][v1.8.2][IMPROVEMENT] Reduce auto balancing logging noise for detached volumes 10692 - @roger-ryao
  • [BACKPORT][v1.8.2][IMPROVEMENT] Improve the Warning Message When Failed to Remove Block-Type Disks 10576 - @yangchiu @ChanYiLin

Bug

Misc

Contributors

Contributors

COLDTURNIP, innobead, and 16 other contributors
Loading

Longhorn v1.8.2-rc3

05 Jun 05:47
@derekbit derekbit
v1.8.2-rc3
2012f4e
Compare
Choose a tag to compare
Longhorn v1.8.2-rc3 Pre-release
Pre-release

DON'T UPGRADE from/to any RC/Preview/Sprint releases because the operation is not supported.

Resolved Issues in this release

Improvement

  • [BACKPORT][v1.8.2][IMPROVEMENT] Adding retry logic for longhorn-csi-plugin when it trying to contact the longhorn-manager pods 11027 - @PhanLe1010 @roger-ryao
  • [BACKPORT][v1.8.2][IMPROVEMENT] add strict field validation to the update option in upgrade path 10648 - @ChanYiLin
  • [BACKPORT][v1.8.2][IMPROVEMENT] Move SettingNameV2DataEngineHugepageLimit to danger zone settings 10568 - @derekbit @chriscchien
  • [BACKPORT][v1.8.2][IMPROVEMENT] Reduce auto balancing logging noise for detached volumes 10692 - @roger-ryao
  • [BACKPORT][v1.8.2][IMPROVEMENT] Improve the Warning Message When Failed to Remove Block-Type Disks 10576 - @yangchiu @ChanYiLin

Bug

Contributors

Contributors

COLDTURNIP, innobead, and 11 other contributors
Loading

Longhorn v1.9.0

27 May 10:01
@derekbit derekbit
v1.9.0
d0ab7f9
Compare
Choose a tag to compare
Longhorn v1.9.0

Longhorn v1.9.0 Release Notes

Longhorn v1.9.0 introduces new features, enhancements, and bug fixes aimed at improving system stability and user experience. Key highlights include V2 Data Engine improvements, orphaned instance deletion, offline replica rebuilding, recurring system backups, and enhanced observability of Longhorn resources.

The Longhorn team appreciates your contributions and anticipates receiving feedback regarding this release.

For terminology and background on Longhorn releases, see Releases.

Warning

The longhorn-manager v1.9.0 is impacted by a regression issue, which causes failures of recurring jobs. To resolve this issue, replace longhorn-manager:v1.9.0 with the hotfixed image longhorn-manager:v1.9.0-hotfix-1.

You can apply the update by following these steps:

  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.9.0 to v1.9.0-hotfix-1 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.

Removal

Environment Check Script

The environment_check.sh script, deprecated in v1.7.0, has been removed in v1.9.0. Use the Longhorn Command Line Tool (longhornctl) to check your environment for potential issues.

Orphan Resource Auto-Deletion

The orphan-auto-deletion setting has been replaced by orphan-resource-auto-deletion in v1.9.0. To replicate the previous behavior, include replica-data in the orphan-resource-auto-deletion value. During the upgrade, the original orphan-auto-deletion setting is automatically migrated.

For more information, see Orphan Data Cleanup.

Deprecated Fields in longhorn.io/v1beta2 CRDs

Deprecated fields have been removed from the CRDs. For details, see issue #6684.

Deprecation & Incompatibilities

longhorn.io/v1beta1 API

The v1beta1 version of the Longhorn API is marked unserved and unsupported in v1.9.0 and will be removed in v1.10.0.

For more details, see Issue #10250.

Breaking Change in V2 Backing Image

Starting with Longhorn v1.9.0, V2 backing images are incompatible with earlier versions due to naming conflicts in the extended attributes (xattrs) used by SPDK backing image logical volumes. As a result, V2 backing images must be deleted and recreated during the upgrade process. Since backing images cannot be deleted while volumes using them still exist, you must first back up, delete, and later restore those volumes as the following steps:

  • Before upgrading to v1.9.0:
    • Verify that backup targets are functioning properly.
    • Create full backups of all volumes that use a V2 backing image.
    • Detach and delete these volumes after the backups complete.
    • In the Backing Image page, save the specifications of all V2 backing images, including the name and the image source.
    • Delete all V2 backing images.
  • After upgrading:
    • Recreate the V2 backing images using the same names and image sources.
    • Restore the volumes from your backups.

For more details, see Issue #10805.

Primary Highlights

New V2 Data Engine Features

While the V2 Data Engine remains experimental in this release, several core functions have been significantly improved:

  • Support UBLK Frontend: Support for UBLK frontend in the V2 Data Engine, which allows for better performance and resource utilization.
  • Storage Network: Introduces support for storage networks in the V2 Data Engine to allow network segregation.
  • Offline Replica Rebuilding: Support for offline replica rebuilding, which allows degraded volumes to automatically recover replicas even while the volume is detached. This capability ensures high data availability without manual intervention.

Recurring System Backup

Starting with Longhorn v1.9.0, you can create a recurring job for system backup creation.

Documentation | GitHub Issue

Offline Replica Rebuilding

Longhorn introduces offline replica rebuilding, a feature that allows degraded volumes to automatically recover replicas even while the volume is detached. This capability minimizes the need for manual recovery steps, accelerates restoration, and ensures high data availability. By default, offline replica rebuilding is disabled. To enable it, set the offline-replica-rebuilding setting to true in the Longhorn UI or CLI.

Documentation | GitHub Issue

Orphaned Instance Deletion

Longhorn can now track and remove orphaned instances, which are leftover resources like replicas or engines that are no longer associated with an active volume. These instances may accumulate due to unexpected failures or incomplete cleanup.

To reduce resource usage and maintain system performance, Longhorn supports both automatic and manual cleanup. By default, this feature is disabled. To enable it, set the orphan-resource-auto-deletion setting to instance in the Longhorn UI or CLI.

Documentation | GitHub Issue

Improved Metrics for Replica, Engine, and Rebuild Status

Longhorn improves observability with new Prometheus metrics that expose the status and identity of Replica and Engine CRs, along with rebuild activity. These metrics make it easier to monitor rebuilds across the cluster.

For more information, see #10550 and #10722.

Installation

Important

Ensure that your cluster is running Kubernetes v1.25 or later before installing Longhorn v1.9.0.

You can install Longhorn using a variety of tools, including Rancher, Kubectl, and Helm. For more information about installation methods and requirements, see Quick Installation in the Longhorn documentation.

Upgrade

Important

Ensure that your cluster is running Kubernetes v1.25 or later before upgrading from Longhorn v1.8.x to v1.9.0.

Longhorn only allows upgrades from supported versions. For more information about upgrade paths and procedures, see Upgrade in the Longhorn documentation.

Post-Release Known Issues

For information about issues identified after this release, see Release-Known-Issues.

Highlight

Feature

Improvement

Read more

Contributors

COLDTURNIP, innobead, and 29 other contributors
Loading

Longhorn v1.9.0-rc4

26 May 05:43
@derekbit derekbit
v1.9.0-rc4
3d7c9d2
Compare
Choose a tag to compare
Longhorn v1.9.0-rc4 Pre-release
Pre-release

DON'T UPGRADE from/to any RC/Preview/Sprint releases because the operation is not supported.

Resolved Issues in this release

Highlight

Feature

Improvement

Bug

Read more

Contributors

COLDTURNIP, innobead, and 25 other contributors
Loading

Longhorn v1.8.2-rc2

26 May 06:42
@derekbit derekbit
v1.8.2-rc2
fe012a4
Compare
Choose a tag to compare
Longhorn v1.8.2-rc2 Pre-release
Pre-release

DON'T UPGRADE from/to any RC/Preview/Sprint releases because the operation is not supported.

Resolved Issues in this release

Improvement

  • [BACKPORT][v1.8.2][IMPROVEMENT] add strict field validation to the update option in upgrade path 10648 - @ChanYiLin
  • [BACKPORT][v1.8.2][IMPROVEMENT] Move SettingNameV2DataEngineHugepageLimit to danger zone settings 10568 - @derekbit @chriscchien
  • [BACKPORT][v1.8.2][IMPROVEMENT] Reduce auto balancing logging noise for detached volumes 10692 - @roger-ryao
  • [BACKPORT][v1.8.2][IMPROVEMENT] Improve the Warning Message When Failed to Remove Block-Type Disks 10576 - @yangchiu @ChanYiLin

Bug

  • [BUG] V2 Backing image failed after upgrade from v1.8.1 to v1.8.2-rc1 10969 - @COLDTURNIP
  • [BACKPORT][v1.8.2][BUG] Error on git checkout in a container 10975 - @derekbit @chriscchien
  • [BACKPORT][v1.8.2][BUG] Helm persistence.backupTargetName not referenced in storageclass template 10964 - @yangchiu @mantissahz
  • [BACKPORT][v1.8.2][BUG] MultiUnmapper floods logs with warnings about size mismatch. 10565 - @shuo-wu @roger-ryao
  • [BACKPORT][v1.8.2][BUG] Test case test_snapshot_prune_and_coalesce_simultaneously_with_backing_image fails 10822 - @yangchiu @c3y1huang
  • [BACKPORT][v1.8.2][BUG] System backup could get stuck in CreatingBackingImageBackups indefinitely 10748 - @yangchiu @ChanYiLin
  • [BACKPORT][v1.8.2][BUG] Failed to terminate namesapce longhorn-system if there is a support bundle ReadyForDownload 10732 - @yangchiu @c3y1huang
  • [BACKPORT][v1.8.2][BUG] [v1.9.0-rc1] DR volume does not sync with latest backup when activation 10842 - @c3y1huang @chriscchien
  • [BACKPORT][v1.8.2][BUG] Can NOT delete an oversized Not Ready volume 10742 - @WebberHuang1118 @chriscchien
  • [BACKPORT][v1.8.2][BUG][UI] Bulk backup creation with a detached volume returns error 405 and error messages show in browser console 10725 - @yangchiu @a110605
  • [BACKPORT][v1.8.2][BUG] Naming collision when creating the name of the new backing image manager 10618 - @yangchiu @ChanYiLin
  • [BACKPORT][v1.8.2][BUG] I/O errors on Longhorn v1.7.2 volume during VM migration while upgrading Harvester v1.4.1 10549 - @derekbit @roger-ryao
  • [BACKPORT][v1.8.2][BUG] Adding a non-existing disk to a node will cause the longhorn-manager to crash 10750 - @ChanYiLin @roger-ryao
  • [BACKPORT][v1.8.2][BUG] After node down and force delete the terminating deployment pod, volume can not attach success 10713 - @c3y1huang @chriscchien
  • [BACKPORT][v1.8.2][BUG] Instance manager image build fail 10654 - @shuo-wu
  • [BACKPORT][v1.8.2][BUG] Longhorn Volume Encryption Not Working in Talos 1.9.x 10605 - @c3y1huang @roger-ryao
  • [BACKPORT][v1.8.2][BUG] integer divide by zero in replica scheduler 10504 - @c3y1huang

Contributors

Contributors

COLDTURNIP, innobead, and 10 other contributors
Loading