-
## Describe the bug
A clear and concise description of what the bug is.
## To Reproduce
Steps to reproduce the behavior:
1. Create a k8s Job that connects to storage shared among multiple do…
gp187 updated
2 years ago
-
## Describe the bug (🐛 if you encounter this issue)
I am using longhorn 1.3.0 for nearly 6 months. Sometimes I have volumes stucked read-only. Then I deleted the pods or recovered the volumes from ba…
-
**Describe the bug**
When Harvester is idling (zero guest vms) it's using a lot of CPU.
```
# kubectl top pods --sort-by=cpu -A | head -n15
W0211 14:45:21.726196 11363 top_pod.go:140] Using …
-
**Describe the bug**
Have a node that has disk pressure, cannot delete any replicas to clean up space.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to Longhorn UI
2. Click on Node
…
-
**Question**
We are having the read-only error on our Rancher clusters almost every day. I suspect that it is due to a network instability, but I am having trouble connecting the dots.
I am trying t…
-
**Describe the bug**
Testing `test_ha_salvage_with_backing_image` failed as in:
https://ci.longhorn.io/job/private/job/longhorn-tests-regression/196/testReport/tests/test_backing_image/test_ha_sa…
-
I mentioned this on Slack as well, anyway I thought I'd open an issue about it. I am testing many things at the moment, including various things concerning Longhorn. I *really* like Longhorn, but I am…
-
Once a Helm release is created by Fleet, there does not appear to be a way to tell Fleet to not make any changes without user intervention. Fleet's documentation mentions a ```pause``` property on a b…
dagan updated
4 months ago
-
**RancherOS Version: v1.5.5**
**Where are you running RancherOS? bare-metal**
Hello, I am running rancheros on bare-metal. I am currently booting it off of USB drives due to limited storage opti…
-
**Describe the bug**
Longhorn seems to ignore Default Replica Count when it is set to 1 (to run in a single-node cluster). It still schedule 3 replicas on a volume created through a volume template.…