Release Known Issues

This page is used for tracking outstanding regression issues found in the official feature releases (major/minor).

• Those issues of each release will be planned to fix in the upcoming patch release.
• The workaround for each issue will be provided in the issue comment if possible.

v1.6.1

Issues

v1.6.0

Issues

v1.5.5

TBU

v1.5.4

N/A

v1.5.3

• [BUG] Deadlock for RWX volume if an error occurs in its share-manager pod #7183

v1.5.2

• [BUG] Failing to mount encrypted volumes v1.5.2

v1.5.1

• [BUG] High CPU usage on one node.
• [BUG] Longhorn Instance Manager Memory leak
• [BUG] Longhorn manager pods in 1.5.1 consuming 20GB+ RAM and 3-4 vCPUs

v1.5.0

• [BUG] Upgrade to 1.5.0 failed: validator.longhorn.io denied the request if having orphan resources
• [BUG] Unused webhook and recovery backend deployment left in helm chart
• [BUG] Longhorn Manager Pods CrashLoop after upgrade from 1.4.0 to 1.5.0 while backing up volumes
• [BUG] 1.5.0: AttachVolume.Attach failed for volume, the volume is currently attached to a different node

v1.4.4

TBU

v1.4.2

• [BUG] Unable to create support bundle if the previous one stayed in ReadyForDownload phase

v1.4.1

• [BUG] RWX volume is stuck at detaching when the attached node is down
• [BUG] instance-manager-e emits Wait for process pvc-xxxx to shutdown constantly and failed unamp operation will leads to the controller dead lock
• [BUG] Upgrade engine --> spec.restoreVolumeRecurringJob and spec.snapshotDataIntegrity Unsupported value
• [BUG] Resources such as replicas are somehow not mutated when network is unstable

v1.4.0

• [BUG] System Backup is stuck at Uploading if there are PVs not provisioned by CSI driver
• [BUG] RWX doesn't work with release 1.4.0 due to end grace update error from recovery backend
• [BUG] Memory leak in CSI plugin caused by stuck umount processes if the RWX volume is already gone

v1.3.3

N/A

v1.3.2

N/A

v1.3.1

• [BUG] Error/warning during uninstallation of Longhorn v1.3.1 via manifest

v1.3.0

• [BUG] No new instance manager deployed on the node after v1.3.0 update if there are disks evicted
• [BUG] longhorn-manager cannot start while upgrading if the configmap contains volume-sensitive settings
• [BUG] After updating longhorn to version 1.3.0, only 1 node had problems and I can't even delete it
  • Fix replica's inconsistent storage IP and IP.
  • If the kubernete node is gone, Longhorn doesn’t need to error out in the validating webhook.
• Add preserveUnknownFields: false to crd specs
• [BUG] Longhorn volume stuck in deleting state
• [BUG] can't upgrade engine if a volume was created in Longhorn v1.0 and the volume.spec.dataLocality is ""

v1.2.6

N/A

v1.2.5

N/A