-
kubelet was restarted
this probably caused Longhorn issues
nodes started misbehaving probably due to broken longhorn mounts
df -h was hanging on those nodes
inspecting the output of mount…
-
## Describe the bug
A few weeks ago I recognized an issue with a process using 1 core of the host entirely. Using `htop` I was able to identify the process to be `sh -c ls /data/longhorn && /data/l…
ghost updated
2 years ago
-
Ref: https://github.com/longhorn/longhorn/issues/2329
-
The only way I could get Longhorn working on Flatcar was doing the following steps:
1) systemctl start iscsid, this will create the /etc/iscsi/initiatorname.iscsi file
2) Add to the cluster defini…
-
**Description**
Analysis of the impact of restoring to snapshot in rancher on Longhorn.
**Steps to follow**
1. Set up a rancher cluster.
2. Deploy longhorn on the cluster.
3. Create a cluster s…
-
**Describe the bug**
Integration tests fail sometimes due to the resetting of engine image failure.
**To Reproduce**
Steps to reproduce the behavior:
1. Run longhorn integration test multiple ti…
-
**Describe the bug**
This may be a bit specific to my setup, but I got asked to create a Github issue for it when asking on Slack. When one of the replicas of a volume gets scheduled onto a specific …
-
**Describe the bug**
The Longhorn docs indicate that Kubernetes don't require any special steps for Longhorn nodes. While this is the case with Ubuntu nodes, this is not the case with Oracle Linux …
-
## Describe the bug
After a while my pod dies and does not start again. I get the following events
```
MountVolume. for volume "pvc-6911563e-37e6-4e08-a857-11267216d408" : Expander.NodeExpand f…
-
## Question
> Suggest to use https://github.com/longhorn/longhorn/discussions to ask questions.
## Environment
- Longhorn version: v1.4.0
- Kubernetes version: v1.23.14
- Node config
-…