Applicable versions​

Confirmed with:

• K3s v1.24.8+k3s1 and RKE2 v1.24.8+rke2r1
• Longhorn v1.3.3
• SUSE Linux Enterprise Server 15 SP5

Applicable versions​

All Longhorn versions, but some features are introduced in v1.4.0 or v1.5.0

Applicable versions​

Confirmed in:

• Longhorn v1.3.2 - v1.3.3
• Longhorn v1.4.0 - v1.4.2
• Longhorn v1.5.0

Potentially mitigated in:

• Longhorn v1.4.3
• Longhorn v1.5.1

Complete fix planned in:

• Longhorn v1.4.x
• Longhorn v1.5.x
• Longhorn v1.6.0

Symptoms​

While the root cause is always the same, symptoms can vary depending on other factors (e.g. whether there are multiple

Applicable versions​

All Longhorn versions.

Kubernetes versions before v1.28. A backported PR to v1.27 is awaiting merging.

Symptoms​

In the event of a worker node failure, while hosting active Pods, the Pods are gracefully evicted as the node undergoes downtime and awaits restoration. During this period, the kubelet, which is responsible for managing the node, will generate the following error messages at regular intervals of two seconds.

orphaned pod <pod-uid> found, but error not a directory occurred when trying to remove the volumes dir

Applicable versions​

All Longhorn versions.

Likely environment​

Commonly seen in Fedora downstream distributions (e.g. Fedora, RHEL, Rocky, CentOS, etc.) when container-selinux is updated beyond version 2.189.0. This can happen unexpectedly and can catch administrators off guard.