8000 Releases · longhorn/longhorn · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Releases: longhorn/longhorn

Longhorn v1.9.0-rc2

07 May 10:20
@derekbit derekbit
v1.9.0-rc2
985ad1d
Compare
Choose a tag to compare
Longhorn v1.9.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

Bug

  • [BUG] backup target settings causes longhorn-manager crash loop during upgrade to v1.9.0 10864 - @COLDTURNIP
  • [BUG][v1.9.0-rc1] v2 volumes don't reuse failed replicas as expected after a node goes down 10828 - @yangchiu @shuo-wu
  • [BUG][v1.9.0-rc1] Unexpected orphaned data are created after v2 instance managers deleted 10829 - @yangchiu
  • [BUG] v2 volume with backing image fails to recover to healthy state after deleting instance manager during replica rebuilding 10521 - @yangchiu
  • [BUG] V2 Backing image not ready after upgrade from v1.8.1 to v1.9.x 10805 - @COLDTURNIP @chriscchien
  • [BUG] Test case test_snapshot_prune_and_coalesce_simultaneously_with_backing_image fails 10808 - @yangchiu @c3y1huang
  • [BUG][UI] Snapshots of v2 volume with backing image aren't shown on the Snapshots and Backups graph 10526 - @derekbit @chriscchien
  • [BUG] Deleted orphan data still renders on the page until page refresh 10803 - @COLDTURNIP @chriscchien @houhoucoop
  • [BUG] v2 Engine loops in detaching and attaching state after rebuilding 10396 - @shuo-wu @roger-ryao
  • [BUG] DR volume does not sync with latest backup when activation 10824 - @c3y1huang @chriscchien
  • [BUG][v1.9.0-rc1] While running component resilience robot test suite, a v2 instance manager gets stuck in Terminating state, preventing block disk from being schedulable on this node 10810 - @DamiaSan
  • [BUG][v1.9.0-rc1] Block disks become temporarily unavailable after the upgrading from v1.8.1 to v1.9.0-rc1 10821 - @mantissahz
  • [BUG] Naming collision when creating the name of the new backing image manager 10616 - @yangchiu @ChanYiLin
  • [BUG] v2 volume replica status error after snapshot deletion with Immediate Data Integrity Check Enable...
Read more

Contributors

COLDTURNIP, innobead, and 23 other contributors
Loading

Longhorn v1.9.0-rc1

28 Apr 12:44
@derekbit derekbit
v1.9.0-rc1
bd00755
Compare
Choose a tag to compare
Longhorn v1.9.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

Bug

  • [BUG][v1.9.0-rc1] Unable to delete v2 backing image 10811 -
  • [BUG][v1.9.0-rc1] While running component resilience robot test suite, a v2 instance manager gets stuck in Terminating state, preventing block disk from being schedulable on this node 10810 - @COLDTURNIP
  • [BUG] Test case test_snapshot_prune_and_coalesce_simultaneously_with_backing_image fails 10808 - @c3y1huang
  • [BUG] V2 Backing image not ready after upgrade from v1.8.1 to v1.9.x 10805 - @COLDTURNIP
  • [BUG] v2 volume replica status error after snapshot deletion with Immediate Data Integrity Check Enabled 10798 - @shuo-wu
  • [BUG] Enabling V2 Data Engine setting, v2 instance manager doesn't start after certain negative factor operations 10791 - @COLDTURNIP @yangchiu
  • [BUG] Volume migration negative test cases fail on v2 volumes 10800 -
  • [BUG] spdk emits Device or resource busy while registering lvol checksum calculation 10140 - @shuo-wu @roger-ryao
  • [BUG] Naming collision when creating the name of the new backing image manager 10616 - @yangchiu @ChanYiLin
  • [BUG] v2 Engine loops in detaching and attaching state after rebuilding 10396 - @shuo-wu @roger-ryao
  • [BUG] v2 instance managers keep crashing on master-head arm64 environment 10768 - @yangchiu @PhanLe1010
  • [BUG] Wrong image name in longhorn-images.txt 10774 - @c3y1huang
  • [BUG] Replica auto balance disk in pressure fails on v2 volumes 10551 - @DamiaSan
  • [BUG] Failed to terminate namesapce longhorn-system if there is a support bundle ReadyForDownload 10731 - @yangchiu @c3y1huang
  • [BUG] After node down and force delete the terminating deployment pod, volume can not attach success 10689 - @c3y1huang @chriscchien
  • [BUG] Deleting a replica of one v2 volume will also deg...
Read more

Contributors

COLDTURNIP, innobead, and 20 other contributors
Loading

Longhorn v1.8.1

05 Mar 09:33
@derekbit derekbit
v1.8.1
30f817b
Compare
Choose a tag to compare
Longhorn v1.8.1 Latest
Latest

Longhorn v1.8.1 Release Notes

Longhorn 1.8.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.8.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.7.x or v1.8.x (< v1.8.1) to v1.8.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

Improvement

  • [BACKPORT][v1.8.1][IMPROVEMENT] Support configurable upgrade-responder URL 10439 - @derekbit @roger-ryao
  • [BACKPORT][v1.8.1][IMPROVEMENT] Several warning for unknown reason 10420 - @roger-ryao
  • [BACKPORT][v1.8.1][IMPROVEMENT] Settings change validation should go back to using Volume state to determine "are all volumes detached" 10376 - @yangchiu @james-munson

Bug

  • [BACKPORT][v1.8.1][BUG] csi keeps creating backup if the backup target is unavailable 10510 - @mantissahz @roger-ryao
  • [BACKPORT][v1.8.1][BUG] integer divide by zero in replica scheduler 10506 - @c3y1huang @chriscchien
  • [BACKPORT][v1.8.1][BUG] Leading or trailing spaces in Longhorn UI break search 10508 - @houhoucoop @roger-ryao
  • [BACKPORT][v1.8.1][BUG] When replica rebuilding completed, the progress could be 99 instead of 100 10485 - @shuo-wu @chriscchien
  • [BACKPORT][v1.8.1][BUG] list_backupVolume API could randomly returns failed to find a node that is ready and has the default engine image error 10478 - @yangchiu @mantissahz
  • [BACKPORT][v1.8.1][BUG] nil pointer when the backing image copy is delete from the spec but also gets evicted at the same time 10466 - @yangchiu @ChanYiLin
  • [BACKPORT][v1.8.1][BUG] 2 uninstall pods could be created after uninstall job was created, one failed with deleting-confirmation-flag is set to false error, while the other completed successfully 10484 -
  • [BACKPORT][v1.8.1][BUG][UI] Backup store setting doesn't apply to the cloned volume 10468 - @yangchiu @mantissahz
  • [BACKPORT][v1.8.1][BUG] v2 volume workload FailedMount with message Staging target path /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/xxx/globalmount is no longer valid 10477 -
  • [BACKPORT][v1.8.1][BUG][UI] Bulk backup creation with a detached volume returns error 405 and error messages show in browser console 10462 - @mantissahz
  • [BACKPORT][v1.8.1][BUG] V2 volume fails to cleanup error replica and rebuild new one - test_data_locality_basic 10364 - @shuo-wu @chriscchien
  • [BACKPORT][v1.8.1][BUG] Data lost caused by Longhorn CSI plugin doing a wrong filesystem format action in a rare race condition 10418 - @yangchiu @PhanLe1010
  • [BACKPORT][v1.8.1][BUG] v2 Engine loops in detaching and attaching state after rebuilding 10397 - @shuo-wu
  • [BACKPORT][v1.8.1][BUG] A V2 volume checksum will change after replica rebuilding if the volume created with backing image 10341 - @shuo-wu @chriscchien
  • [BACKPORT][v1.8.1][BUG] Bug in snapshot count enforcement cause volume faulted and stuck in detaching/attaching loop 10309 - @PhanLe1010 @roger-ryao
  • [BACKPORT][v1.8.1][BUG] Test case test_csi_mount_volume_online_expansion is failing due to unable to expand PVC 10414 - @yangchiu @c3y1huang
  • [BACKPORT][v1.8.1][BUG] V2 BackingImage failed after node reboot 10343 - @ChanYiLin @chriscchien
  • [BACKPORT][v1.8.1][BUG] Workload pod will not be able to move to new node when backup operation is taking a long time 10172 - @PhanLe1010 @chriscchien
  • [BACKPORT][v1.8.1][BUG] WebUI Volumes Disappear and Reappear 10332 - @PhanLe1010 @chriscchien @houhoucoop
  • [BACKPORT][v1.8.1][BUG] "Error get size" from "metrics_collector.(*BackupCollector).Collect" on every metric scrape 10361 - @derekbit @chriscchien
  • [BACKPORT][v1.8.1][BUG] [UI] 'Create' button on the System Backup page is disabled after reloading page 10354 - @chriscchien @houhoucoop
  • [BACKPORT][v1.8.1][BUG] Proxy gRPC API ReplicaList returns different output formats for v1 and v2 volumes 10353 - @shuo-wu @roger-ryao
  • [BACKPORT][v1.8.1][BUG] constant attaching/reattaching of volumes after upgrading to 1.8 10315 - @james-munson
  • [BACKPORT][v1.8.1][BUG] Backup Execution Timeout setting issue in Helm chart 10325 - @james-munson @chriscchien
  • [BACKPORT][v1.8.1][BUG] v2 engine stuck in detaching-attaching loop if the previous replica is not cleaned up correct 10363 - @shuo-wu @chriscchien
  • [BACKPORT][v1.8.1][BUG] Longhorn CSI plugin 1.8.0 crashes consistently when trying to create a snapshot 10319 - @PhanLe1010 @chriscchien
  • [BACKPORT][v1.8.1][BUG] Engine stuck in "stopped" state, prevent volume attach 10329 - @ChanYiLin @chriscchien
  • [BACKPORT][v1.8.1][BUG] After upgrading to v1.8.0 the version number lost on the web-ui 10337 - @derekbit
  • [BACKPORT][v1.8.1][BUG] insufficient storage;precheck new replica failed after a temporary shutdown of a node 10234 - @PhanLe1010

Misc

Contributors

Contributors

innobead, asettle, and 15 other contributors
Assets 6
Loading

Longhorn v1.8.1-rc3

04 Mar 05:20
@derekbit derekbit
v1.8.1-rc3
d911754
Compare
Choose a tag to compare
Longhorn v1.8.1-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.1][IMPROVEMENT] Support configurable upgrade-responder URL 10439 - @derekbit @roger-ryao
  • [BACKPORT][v1.8.1][IMPROVEMENT] Several warning for unknown reason 10420 - @roger-ryao
  • [BACKPORT][v1.8.1][IMPROVEMENT] Settings change validation should go back to using Volume state to determine "are all volumes detached" 10376 - @yangchiu @james-munson

Bug

  • [BACKPORT][v1.8.1][BUG] csi keeps creating backup if the backup target is unavailable 10510 - @mantissahz @roger-ryao
  • [BACKPORT][v1.8.1][BUG] integer divide by zero in replica scheduler 10506 - @c3y1huang @chriscchien
  • [BACKPORT][v1.8.1][BUG] Leading or trailing spaces in Longhorn UI break search 10508 - @houhoucoop @roger-ryao
  • [BACKPORT][v1.8.1][BUG] When replica rebuilding completed, the progress could be 99 instead of 100 10485 - @shuo-wu @chriscchien
  • [BACKPORT][v1.8.1][BUG] list_backupVolume API could randomly returns failed to find a node that is ready and has the default engine image error 10478 - @yangchiu @mantissahz
  • [BACKPORT][v1.8.1][BUG] nil pointer when the backing image copy is delete from the spec but also gets evicted at the same time 10466 - @yangchiu @ChanYiLin
  • [BACKPORT][v1.8.1][BUG] 2 uninstall pods could be created after uninstall job was created, one failed with deleting-confirmation-flag is set to false error, while the other completed successfully 10484 -
  • [BACKPORT][v1.8.1][BUG][UI] Backup store setting doesn't apply to the cloned volume 10468 - @yangchiu @mantissahz
  • [BACKPORT][v1.8.1][BUG] v2 volume workload FailedMount with message Staging target path /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/xxx/globalmount is no longer valid 10477 -
  • [BACKPORT][v1.8.1][BUG][UI] Bulk backup creation with a detached volume returns error 405 and error messages show in browser console 10462 - @mantissahz
  • [BACKPORT][v1.8.1][BUG] V2 volume fails to cleanup error replica and rebuild new one - test_data_locality_basic 10364 - @shuo-wu @chriscchien
  • [BACKPORT][v1.8.1][BUG] Data lost caused by Longhorn CSI plugin doing a wrong filesystem format action in a rare race condition 10418 - @yangchiu @PhanLe1010
  • [BACKPORT][v1.8.1][BUG] v2 Engine loops in detaching and attaching state after rebuilding 10397 - @shuo-wu
  • [BACKPORT][v1.8.1][BUG] A V2 volume checksum will change after replica rebuilding if the volume created with backing image 10341 - @shuo-wu @chriscchien
  • [BACKPORT][v1.8.1][BUG] Bug in snapshot count enforcement cause volume faulted and stuck in detaching/attaching loop 10309 - @PhanLe1010 @roger-ryao
  • [BACKPORT][v1.8.1][BUG] Test case test_csi_mount_volume_online_expansion is failing due to unable to expand PVC 10414 - @yangchiu @c3y1huang
  • [BACKPORT][v1.8.1][BUG] V2 BackingImage failed after node reboot 10343 - @ChanYiLin @chriscchien
  • [BACKPORT][v1.8.1][BUG] Workload pod will not be able to move to new node when backup operation is taking a long time 10172 - @PhanLe1010 @chriscchien
  • [BACKPORT][v1.8.1][BUG] WebUI Volumes Disappear and Reappear 10332 - @PhanLe1010 @chriscchien @houhoucoop
  • [BACKPORT][v1.8.1][BUG] "Error get size" from "metrics_collector.(*BackupCollector).Collect" on every metric scrape 10361 - @derekbit @chriscchien
  • [BACKPORT][v1.8.1][BUG] [UI] 'Create' button on the System Backup page is disabled after reloading page 10354 - @chriscchien @houhoucoop
  • [BACKPORT][v1.8.1][BUG] Proxy gRPC API ReplicaList returns different output formats for v1 and v2 volumes 10353 - @shuo-wu @roger-ryao
  • [BACKPORT][v1.8.1][BUG] constant attaching/reattaching of volumes after upgrading to 1.8 10315 - @james-munson
  • [BACKPORT][v1.8.1][BUG] Backup Execution Timeout setting issue in Helm chart 10325 - @james-munson @chriscchien
  • [BACKPORT][v1.8.1][BUG] v2 engine stuck in detaching-attaching loop if the previous replica is not cleaned up correct 10363 - @shuo-wu @chriscchien
  • [BACKPORT][v1.8.1][BUG] Longhorn CSI plugin 1.8.0 crashes consistently when trying to create a snapshot 10319 - @PhanLe1010 @chriscchien
  • [BACKPORT][v1.8.1][BUG] Engine stuck in "stopped" state, prevent volume attach 10329 - @ChanYiLin @chriscchien
  • [BACKPORT][v1.8.1][BUG] After upgrading to v1.8.0 the version number lost on the web-ui 10337 - @derekbit
  • [BACKPORT][v1.8.1][BUG] insufficient storage;precheck new replica failed after a temporary shutdown of a node 10234 - @PhanLe1010

Misc

Contributors

Contributors

innobead, yangchiu, and 10 other contributors
Loading

Longhorn v1.8.1-rc2

26 Feb 10:27
@derekbit derekbit
v1.8.1-rc2
eb584b5
Compare
8000 Choose a tag to compare
Longhorn v1.8.1-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.1][IMPROVEMENT] Support configurable upgrade-responder URL 10439 - @derekbit @roger-ryao
  • [BACKPORT][v1.8.1][IMPROVEMENT] Several warning for unknown reason 10420 - @roger-ryao
  • [BACKPORT][v1.8.1][IMPROVEMENT] Settings change validation should go back to using Volume state to determine "are all volumes detached" 10376 - @yangchiu @james-munson

Bug

  • [BACKPORT][v1.8.1][BUG] When replica rebuilding completed, the progress could be 99 instead of 100 10485 - @shuo-wu @chriscchien
  • [BACKPORT][v1.8.1][BUG] list_backupVolume API could randomly returns failed to find a node that is ready and has the default engine image error 10478 - @yangchiu @mantissahz
  • [BACKPORT][v1.8.1][BUG] nil pointer when the backing image copy is delete from the spec but also gets evicted at the same time 10466 - @yangchiu @ChanYiLin
  • [BACKPORT][v1.8.1][BUG] 2 uninstall pods could be created after uninstall job was created, one failed with deleting-confirmation-flag is set to false error, while the other completed successfully 10484 -
  • [BACKPORT][v1.8.1][BUG][UI] Backup store setting doesn't apply to the cloned volume 10468 - @yangchiu @mantissahz
  • [BACKPORT][v1.8.1][BUG] v2 volume workload FailedMount with message Staging target path /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/xxx/globalmount is no longer valid 10477 -
  • [BACKPORT][v1.8.1][BUG][UI] Bulk backup creation with a detached volume returns error 405 and error messages show in browser console 10462 - @mantissahz
  • [BACKPORT][v1.8.1][BUG] V2 volume fails to cleanup error replica and rebuild new one - test_data_locality_basic 10364 - @shuo-wu @chriscchien
  • [BACKPORT][v1.8.1][BUG] Data lost caused by Longhorn CSI plugin doing a wrong filesystem format action in a rare race condition 10418 - @yangchiu @PhanLe1010
  • [BACKPORT][v1.8.1][BUG] v2 Engine loops in detaching and attaching state after rebuilding 10397 - @shuo-wu
  • [BACKPORT][v1.8.1][BUG] A V2 volume checksum will change after replica rebuilding if the volume created with backing image 10341 - @shuo-wu @chriscchien
  • [BACKPORT][v1.8.1][BUG] Bug in snapshot count enforcement cause volume faulted and stuck in detaching/attaching loop 10309 - @PhanLe1010 @roger-ryao
  • [BACKPORT][v1.8.1][BUG] Test case test_csi_mount_volume_online_expansion is failing due to unable to expand PVC 10414 - @yangchiu @c3y1huang
  • [BACKPORT][v1.8.1][BUG] V2 BackingImage failed after node reboot 10343 - @ChanYiLin @chriscchien
  • [BACKPORT][v1.8.1][BUG] Workload pod will not be able to move to new node when backup operation is taking a long time 10172 - @PhanLe1010 @chriscchien
  • [BACKPORT][v1.8.1][BUG] WebUI Volumes Disappear and Reappear 10332 - @PhanLe1010 @chriscchien @houhoucoop
  • [BACKPORT][v1.8.1][BUG] "Error get size" from "metrics_collector.(*BackupCollector).Collect" on every metric scrape 10361 - @derekbit @chriscchien
  • [BACKPORT][v1.8.1][BUG] [UI] 'Create' button on the System Backup page is disabled after reloading page 10354 - @chriscchien @houhoucoop
  • [BACKPORT][v1.8.1][BUG] Proxy gRPC API ReplicaList returns different output formats for v1 and v2 volumes 10353 - @shuo-wu @roger-ryao
  • [BACKPORT][v1.8.1][BUG] constant attaching/reattaching of volumes after upgrading to 1.8 10315 - @james-munson
  • [BACKPORT][v1.8.1][BUG] Backup Execution Timeout setting issue in Helm chart 10325 - @james-munson @chriscchien
  • [BACKPORT][v1.8.1][BUG] v2 engine stuck in detaching-attaching loop if the previous replica is not cleaned up correct 10363 - @shuo-wu @chriscchien
  • [BACKPORT][v1.8.1][BUG] Longhorn CSI plugin 1.8.0 crashes consistently when trying to create a snapshot 10319 - @PhanLe1010 @chriscchien
  • [BACKPORT][v1.8.1][BUG] Engine stuck in "stopped" state, prevent volume attach 10329 - @ChanYiLin @chriscchien
  • [BACKPORT][v1.8.1][BUG] After upgrading to v1.8.0 the version number lost on the web-ui 10337 - @derekbit
  • [BACKPORT][v1.8.1][BUG] insufficient storage;precheck new replica failed after a temporary shutdown of a node 10234 - @PhanLe1010

Misc

Contributors

Contributors

innobead, yangchiu, and 10 other contributors
Loading

Longhorn v1.8.1-rc1

19 Feb 12:58
@derekbit derekbit
v1.8.1-rc1
5339df5
Compare
Choose a tag to compare
Longhorn v1.8.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

Improvement

  • [BACKPORT][v1.8.1][IMPROVEMENT] Support configurable upgrade-responder URL 10439 - @derekbit @roger-ryao
  • [BACKPORT][v1.8.1][IMPROVEMENT] Several warning for unknown reason 10420 - @roger-ryao
  • [BACKPORT][v1.8.1][IMPROVEMENT] Settings change validation should go back to using Volume state to determine "are all volumes detached" 10376 - @yangchiu @james-munson

Bug

  • [BACKPORT][v1.8.1][BUG] V2 volume fails to cleanup error replica and rebuild new one - test_data_locality_basic 10364 - @shuo-wu @chriscchien
  • [BACKPORT][v1.8.1][BUG] Data lost caused by Longhorn CSI plugin doing a wrong filesystem format action in a rare race condition 10418 - @yangchiu @PhanLe1010
  • [BACKPORT][v1.8.1][BUG] v2 Engine loops in detaching and attaching state after rebuilding 10397 - @shuo-wu
  • [BACKPORT][v1.8.1][BUG] A V2 volume checksum will change after replica rebuilding if the volume created with backing image 10341 - @shuo-wu @chriscchien
  • [BACKPORT][v1.8.1][BUG] Bug in snapshot count enforcement cause volume faulted and stuck in detaching/attaching loop 10309 - @PhanLe1010 @roger-ryao
  • [BACKPORT][v1.8.1][BUG] Test case test_csi_mount_volume_online_expansion is failing due to unable to expand PVC 10414 - @yangchiu @c3y1huang
  • [BACKPORT][v1.8.1][BUG] V2 BackingImage failed after node reboot 10343 - @ChanYiLin @chriscchien
  • [BACKPORT][v1.8.1][BUG] Workload pod will not be able to move to new node when backup operation is taking a long time 10172 - @PhanLe1010 @chriscchien
  • [BACKPORT][v1.8.1][BUG] WebUI Volumes Disappear and Reappear 10332 - @PhanLe1010 @chriscchien @houhoucoop
  • [BACKPORT][v1.8.1][BUG] "Error get size" from "metrics_collector.(*BackupCollector).Collect" on every metric scrape 10361 - @derekbit @chriscchien
  • [BACKPORT][v1.8.1][BUG] [UI] 'Create' button on the System Backup page is disabled after reloading page 10354 - @chriscchien @houhoucoop
  • [BACKPORT][v1.8.1][BUG] Proxy gRPC API ReplicaList returns different output formats for v1 and v2 volumes 10353 - @shuo-wu @roger-ryao
  • [BACKPORT][v1.8.1][BUG] constant attaching/reattaching of volumes after upgrading to 1.8 10315 - @james-munson
  • [BACKPORT][v1.8.1][BUG] Backup Execution Timeout setting issue in Helm chart 10325 - @james-munson @chriscchien
  • [BACKPORT][v1.8.1][BUG] v2 engine stuck in detaching-attaching loop if the previous replica is not cleaned up correct 10363 - @shuo-wu @chriscchien
  • [BACKPORT][v1.8.1][BUG] Longhorn CSI plugin 1.8.0 crashes consistently when trying to create a snapshot 10319 - @PhanLe1010 @chriscchien
  • [BACKPORT][v1.8.1][BUG] Engine stuck in "stopped" state, prevent volume attach 10329 - @ChanYiLin @chriscchien
  • [BACKPORT][v1.8.1][BUG] After upgrading to v1.8.0 the version number lost on the web-ui 10337 - @derekbit
  • [BACKPORT][v1.8.1][BUG] insufficient storage;precheck new replica failed after a temporary shutdown of a node 10234 - @PhanLe1010

Misc

Contributors

Contributors

innobead, yangchiu, and 9 other contributors
Loading

Longhorn v1.7.3

19 Feb 08:49
@derekbit derekbit
v1.7.3
76fb3e7
Compare
Choose a tag to compare
Longhorn v1.7.3

Longhorn v1.7.3 Release Notes

Longhorn 1.7.3 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.21 or later before installing Longhorn v1.7.3.

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.21 or later before upgrading from Longhorn v1.6.x or v1.7.x (< v1.7.0) to v1.7.3.

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

Deprecation & Incompatibilities

The functionality of the environment check script overlaps with that of the Longhorn CLI, which is available starting with v1.7.0. Because of this, the script is deprecated in v1.7.0 and is scheduled for removal in v1.8.0.

For information about important changes, including feature incompatibility, deprecation, and removal, see Important Notes in the Longhorn documentation.

Post-Release Known Issues

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

Resolved Issues

Feature

  • [BACKPORT][v1.7.3][FEATURE] Add periodic HugePages (2Mi) configuration check to ensure v2 data engine compatibility 10029 - @jangseon-ryu @yangchiu

Improvement

  • [BACKPORT][v1.7.3][IMPROVEMENT] Settings change validation should go back to using Volume state to determine "are all volumes detached" 10375 - @yangchiu @james-munson
  • [BACKPORT][v1.7.3][IMPROVEMENT] Add support for JSON log format configuration in Longhorn components (UI, driver) 10082 - @chriscchien
  • [BACKPORT][v1.7.3][IMPROVEMENT] Logging the reason why the instance manager pod is going to be deleted. 9887 - @derekbit @chriscchien
  • [BACKPORT][v1.7.3][IMPROVEMENT] Why is it not possible to change the replica count in v2 longhorn volume? 9806 - @chriscchien
  • [BACKPORT][v1.7.3][IMPROVEMENT] Check NFS versions in /etc/nfsmount.conf instead 9831 - @COLDTURNIP @roger-ryao
  • [BACKPORT][v1.7.3][IMPROVEMENT] Add dmsetup and dmcrypt utilities check in cli 9935 - @COLDTURNIP @roger-ryao
  • [BACKPORT][v1.7.3][UI][IMPROVEMENT] Improve the volume size information on UI 9964 - @houhoucoop @roger-ryao
  • [BACKPORT][v1.7.3][IMPROVEMENT] Prevent Volume Resize Stuck 9914 - @c3y1huang @roger-ryao
  • [BACKPORT][v1.7.3][IMPROVEMENT][UI] Add backupBackingImage table in backup page with tabs 9970 - @houhoucoop
  • [BACKPORT][v1.7.3][IMPROVEMENT] Reject strict-local + RWX volume creation 9930 - @COLDTURNIP @yangchiu
  • [BACKPORT][v1.7.3][IMPROVEMENT] Configure the log level of other system and user managed components via longhorn manager setting 9617 - @yangchiu @james-munson
  • [BACKPORT][v1.7.3][IMPROVEMENT] Change confusing error message to warning level 9917 - @yangchiu @derekbit
  • [BACKPORT][v1.7.3][IMPROVEMENT] Building longhorn-manager takes long time 9693 - @derekbit @chriscchien
  • [BACKPORT][v1.7.3][IMPROVEMENT] Talos support for environment check in longhorn manager 9723 - @yangchiu @c3y1huang

Bug

Read more

Contributors

COLDTURNIP, innobead, and 17 other contributors
Loading

Longhorn v1.7.3-rc2

17 Feb 12:11
@derekbit derekbit
v1.7.3-rc2
86bc412
Compare
Choose a tag to compare
Longhorn v1.7.3-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

Feature

  • [BACKPORT][v1.7.3][FEATURE] Add periodic HugePages (2Mi) configuration check to ensure v2 data engine compatibility 10029 - @yangchiu

Improvement

  • [BACKPORT][v1.7.3][IMPROVEMENT] Settings change validation should go back to using Volume state to determine "are all volumes detached" 10375 - @yangchiu @james-munson
  • [BACKPORT][v1.7.3][IMPROVEMENT] Add support for JSON log format configuration in Longhorn components (UI, driver) 10082 - @chriscchien
  • [BACKPORT][v1.7.3][IMPROVEMENT] Logging the reason why the instance manager pod is going to be deleted. 9887 - @derekbit @chriscchien
  • [BACKPORT][v1.7.3][IMPROVEMENT] Why is it not possible to change the replica count in v2 longhorn volume? 9806 - @chriscchien
  • [BACKPORT][v1.7.3][IMPROVEMENT] Check NFS versions in /etc/nfsmount.conf instead 9831 - @COLDTURNIP @roger-ryao
  • [BACKPORT][v1.7.3][IMPROVEMENT] Add dmsetup and dmcrypt utilities check in cli 9935 - @COLDTURNIP @roger-ryao
  • [BACKPORT][v1.7.3][UI][IMPROVEMENT] Improve the volume size information on UI 9964 - @houhoucoop @roger-ryao
  • [BACKPORT][v1.7.3][IMPROVEMENT] Prevent Volume Resize Stuck 9914 - @c3y1huang @roger-ryao
  • [BACKPORT][v1.7.3][IMPROVEMENT][UI] Add backupBackingImage table in backup page with tabs 9970 - @houhoucoop
  • [BACKPORT][v1.7.3][IMPROVEMENT] Reject strict-local + RWX volume creation 9930 - @COLDTURNIP @yangchiu
  • [BACKPORT][v1.7.3][IMPROVEMENT] Configure the log level of other system and user managed components via longhorn manager setting 9617 - @yangchiu @james-munson
  • [BACKPORT][v1.7.3][IMPROVEMENT] Change confusing error message to warning level 9917 - @yangchiu @derekbit
  • [BACKPORT][v1.7.3][IMPROVEMENT] Building longhorn-manager takes long time 9693 - @derekbit @chriscchien
  • [BACKPORT][v1.7.3][IMPROVEMENT] Talos support for environment check in longhorn manager 9723 - @yangchiu @c3y1huang

Bug

Misc

Contributors

Contributors

COLDTURNIP, innobead, and 11 other contributors
Loading

Longhorn v1.8.0

22 Jan 07:50
@derekbit derekbit
v1.8.0
7c7c779
Compare
Choose a tag to compare
Longhorn v1.8.0

Longhorn v1.8.0 Release Notes

This latest version of Longhorn introduces several features, enhancements, and bug fixes that are intended to improve system quality and the overall user experience. Highlights include new V2 Data Engine features, multiple backupstores, automatic RWX volume expansion, installation and upgrades via Helm Controller, and V2 Data Engine Support for Talos Linux.

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

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

Warning

An incorrect Longhorn image tag (v1.8.x-head) was used in the deployment manifest and the Helm chart. The correct tag for Longhorn v1.8.0 images is v1.8.0. For more information, see Issue #10336.

If you installed or upgraded Longhorn using the deployment manifest or the Helm chart from the main Longhorn repository, perform the following actions to resolve the issue:

  • New installations: Replace v1.8.x-head with v1.8.0 in the deployment manifest or the Helm chart before deploying Longhorn.

  • Upgrades: Replace v1.8.x-head with v1.8.0 in the deployment manifest or Helm chart. Next, upgrade the Longhorn system and update the engine image for volumes that use v1.8.x-head.

This issue does not affect installations and upgrades performed using the Longhorn Helm repository. For more details, refer to the Install with Helm section of the official documentation.

Important

The CSI external-snapshotter was upgraded to v8.2.0. Ensure that all clusters are running Kubernetes v1.25 or later before upgrading to Longhorn v1.8.0 or a later version.

Deprecation & Incompatibilities

  • The default block size for block-type disks in earlier Longhorn releases is 4096 bytes. However, 512 bytes is more commonly used and aligns with the V1 Data Engine's configuration. Additionally, the 4096-byte block size is incompatible with backing images generated by the V1 Data Engine. To address these concerns, the default block size was changed to 512 bytes.

    If you have existing V2 volumes, perform the following steps:

    1. Back up the V2 volumes.
    2. Remove the V2 volumes.
    3. Delete the block-type disk with a 4096-byte block size from node.spec.disks.
    4. Erase the old data on the block-type disk using tools such as dd.
    5. Add the disk again to node.spec.disks with the updated configuration.
    6. Restore the V2 volumes.

    For more information, see #10053.

  • A V2 volume data corruption issue that affects earlier Longhorn releases has been resolved in v1.8.0. The issue involves potential continual changes to the checksum of files in a V2 volume with multiple replicas. This occurs because SPDK allocates clusters without initialization, leading to data inconsistencies across replicas. The varying data read from the volume can result in data corruption and broken backups. For more information, see #10035.

Primary Highlights

New V2 Data Engine Features

Although the V2 Data Engine is still considered an experimental feature in this release, the core functions have been significantly enhanced.

Multiple Backupstores and Default Backup Target

Starting with v1.8.0, Longhorn allows you to use multiple backupstores for storing backups of Longhorn volumes. Longhorn v1.8.0 also creates a default backup target (default) during installation and upgrades. The default backup target is used for system backups and volumes that were created without an assigned backup target name.

Demo | Documentation | GitHub Issue

Automatic RWX Volume Expansion

Longhorn v1.8.0 supports fully automatic online expansion of RWX volumes without the need to scale down the workload or apply manual commands. To use this feature, ensure that the v1.8.0 versions of Longhorn Manager, Share Manager, and the CSI plugin are all running.

Documentation | GitHub Issue

Helm Controller

You can now install and upgrade Longhorn on clusters running RKE2 or K3s using the Helm Controller that is built into those distributions. The Helm Controller manages Helm charts using a HelmChart Custom Resource Definition (CRD), which contains most of the options that would normally be passed to the Helm command-line tool.

Documentation | GitHub Issue

V2 Data Engine Support for Talos Linux

Longhorn v1.8.0 supports usage of V2 volumes in Talos Linux clusters. To use this feature, ensure that all nodes meet the V2 Data Engine prerequisites.

Documentation | GitHub Issue

Installation

Important

Ensure that your cluster is running Kubernetes v1.25 or later before installing Longhorn v1.8.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.7.x to v1.8.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

  • [FEATURE] Support Data Engine Option For Backing Image in CSI flow 10084 - @ChanYiLin @roger-ryao
  • [FEATURE] Missing option to modify backup-task retain value from UI while editing recurring job [8810](#8810...
Read more

Contributors

COLDTURNIP, tserong, and 26 other contributors
Loading

Longhorn v1.8.0-rc5

20 Jan 08:41
@derekbit derekbit
v1.8.0-rc5
d86e2e7
Compare
Choose a tag to compare
Longhorn v1.8.0-rc5 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, tserong, and 21 other contributors
Loading
0