-
## Is your improvement request related to a feature? Please describe (👍 if you like this request)
Before upgrading Longhorn, certain prerequisites must be met, such as detaching all v2 volumes, to …
-
## Describe the bug
Longhorn (v2) with a 20TB disk request is not properly being provisioned.
`[longhorn-instance-manager] time="2024-07-16T08:35:48Z" level=error msg="Failed to create engine pv…
-
## Describe the bug
While redeploying as Statefulset, the first Pod is unable to attach the volume with the following error message:
0s Warning FailedMapVolume pod/aerospike-0 …
-
## Describe the bug
Recently upgraded from Longhorn 1.6.0 to Longhorn 1.6.2 after which I started experiencing issues attaching nodes, also seeing issues with volumes completing their upgrade/runni…
-
## Describe the bug
When I click on "Backup" in the Longhorn dashboard. I get the following error message:
`error listing backup volume names: timeout executing: /var/lib/longhorn/engine-binaries…
-
## Is your improvement request related to a feature? Please describe (👍 if you like this request)
The Longhorn CLI help menu descriptions are currently written by developers. It would be great if w…
-
**Is your feature request related to a problem? Please describe.**
We have multiple Harvester clusters in multiple datacenters. Managing them all with Rancher is convenient but dealing with images b…
-
## Describe the bug
When the k3s-agent service on a worker node is restarted, or if a worker node becomes temporarily unreachable, Kubernetes will attempt to move the workload to another scheduled …
-
**Is your enhancement related to a problem? Please describe.**
We should improve the situation that multiple volumes try to attach to the workload simultaneously on the downstream cluster.
There are…
-
**Describe the bug**
v1.3.1 -> v1.3.2-rc2 upgrade fail on 2 nodes clusters with customized default storage class and VM
**To Reproduce**
1.
Fresh install 2 nodes harvester-v1.3.1
…