longhorn: [BUG] Volumes provisioned with the `longhorn` storage class don't show up in the Longhorn UI

Describe the bug Volumes provisioned with the longhorn storage class don’t show up in the Longhorn UI.

I also just tried adding a default backup target in https://github.com/sseneca/sserver/commit/0b1a186b627228f2e1136b5b76ba02266423e799 but I get backup target URL is empty, even though the change is present in the ConfigMap?

To Reproduce Steps to reproduce the behavior:

Install longhorn onto cluster (https://github.com/sseneca/sserver/commit/9f90542708fdfe817862561eab38f57aa3adb208)
Provision longhorn PVs (https://github.com/sseneca/sserver/commit/673529fb1ddd4649ae6d0a443ccd37e5539d905a)
Go to UI. It shows “No Volume”

Expected behavior Ability to view the newly provisioned volumes in the UI.

Log

No interesting logs from the UI pod, not sure if you want logs from the manager?

Environment:

Longhorn version: v1.2.2
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): Helm
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: k3s v1.21.5+k3s2
- Number of management node in the cluster: 1
- Number of worker node in the cluster: n/a (single node cluster)
Node config
- OS type and version: Linux sserver 5.10.72-gnu1-1-lts #1 SMP Mon, 11 Oct 2021 22:35:29 +0000 x86_64 GNU/Linux
- CPU per node: Intel i5-4690 (4) @ 3.900GHz
- Memory per node: 7824MiB
- Disk type(e.g. SSD/NVMe): 2x 3TB btrfs drives in RAID 1 (1.5TB usable space)
- Network bandwidth between the nodes: n/a
Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): Baremetal
Number of Longhorn volumes in the cluster: 5 as of writing

About this issue

Original URL
State: open
Created 3 years ago
Comments: 22 (12 by maintainers)

Most upvoted comments

Hi,

Sorry for beign a longhorn noob, I just didn’t create the “exixsting volume” referenced in the pv’s definition in the example above. Once understood that using a pv needs an already existing volume, everything works flawlessly.

Thank you and sorry again for the improper report.

urbaman on May 9, 2023

I think now Longhorn is not well support on GitOps tool.

There are PVs/PVCs using longhorn StorageClass, but can’t see it under Volume CRs (volumes.longhorn.io) 🤔

jenting on Nov 1, 2021

Doing kubectl get volumes -n longhorn-system returns nothing, as does doing kubectl get volumes -A. But if I do kubectl get pv, it lists the persistent volumes with the longhorn storage class. Not sure why no volumes exist, despite PersistentVolumes with the longhorn storage class existing?

sseneca on Oct 29, 2021