CARVIEW |
Navigation Menu
-
Notifications
You must be signed in to change notification settings - Fork 647
Longhorn v1.7.1
Compare
Longhorn v1.7.1 Release Notes
Longhorn 1.7.1 introduces several improvements and bug fixes that are intended to improve system quality, resilience, and stability.
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.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.21 or later before upgrading from Longhorn v1.6.x or v1.7.x (< v1.7.0) to v1.7.1.
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
Improvement
- [BACKPORT][v1.7.1][IMPROVEMENT] Longhorn CLI should install
cryptsetup
9316 - @mantissahz @roger-ryao - [BACKPORT][v1.7.1][IMPROVEMENT] Resilience handling for the last replica timeout 9275 - @ejweber @chriscchien
- [BACKPORT][v1.7.1][IMPROVEMENT] Check kernel module
dm_crypt
on host machines 9310 - @mantissahz
Bug
- [BACKPORT][v1.7.1][BUG] Fix security issues in v1.7.1 RC images 9363 - @c3y1huang
- [BACKPORT][v1.7.1][BUG] should set backing image minNumberOfCopies to 1 when upgrading Longhorn 9353 - @ChanYiLin @chriscchien
- [BACKPORT][v1.7.1][BUG] System Backup Fails and DR Volume Enters Attach-Detach Loop When Volume Backup Policy is Set to
Always
9333 - @c3y1huang @roger-ryao - [BACKPORT][v1.7.1][BUG] [Backupstore] Need to close the reader after downloading files for the Azure backup store driver. 9282 - @yangchiu @mantissahz
- [BACKPORT][v1.7.1][BUG] Unable to access azurite backup store by DNS hostname 9341 - @mantissahz
- [BACKPORT][v1.7.1][BUG] v1 volume replica rebuild fail after upgrade from v1.7.0 to v1.7.1-rc1 9332 - @PhanLe1010 @chriscchien
- [BACKPORT][v1.7.1][BUG] v2-data-engine setting validator doesn't take disabled nodes into account when checking hugepages 9320 - @tserong @roger-ryao
- [BACKPORT][v1.7.1][BUG] Some volumes stuck in "Attaching" state after upgrade to 1.7.0 9270 - @ChanYiLin @roger-ryao
- [BACKPORT][v1.7.1][BUG] error logs appeared in uninstallation job 9304 - @ChanYiLin @chriscchien
- [BACKPORT][v1.7.1][BUG] Incorrect NFS endpoint after enable/disable storage network for RWX volume 9273 - @Vicente-Cheng @roger-ryao
- [BACKPORT][v1.7.1][BUG] Volume stuck in degraded 9285 - @PhanLe1010 @chriscchien
- [BACKPORT][v1.7.1][BUG] LH fails silently when node has attached volumes 9210 - @ejweber @chriscchien