Volumes broken in the UI

Nomad
1

Hi all,

currently having the problem with Nomad for some time that the registered volumes are not displaying at all. Seems to be a pure UI problems, the volumes themselves are working fine.
I can go to
http://master.home:4646/ui/csi/volumes
to display the list of registered volumes just fine. A
nomad volume status
also returns valid information.

Unfortunately, when I click on a volume in the UI, I get a “not found” for the volume details.
URL for the reqeuest
http://master.home:4646/ui/csi/volumes/gitea@default
“nomad volume status gitea” output

ID                   = gitea
Name                 = Gitea
Namespace            = default
External ID          = <none>
Plugin ID            = nfs
Provider             = nfs.csi.k8s.io
Version              = v4.3.0
Capacity             = 0 B
Schedulable          = true
Controllers Healthy  = 2
Controllers Expected = 2
Nodes Healthy        = 5
Nodes Expected       = 5
Access Mode          = single-node-writer
Attachment Mode      = file-system
Mount Options        = fs_type: nfs flags: [REDACTED]
Namespace            = default

Allocations
ID        Node ID   Task Group  Version  Desired  Status   Created     Modified
c42c925f  c1e29920  gitea       47       run      running  11d16h ago  11d16h ago

Nomad version is 1.8.3 (latest)

Unfortunately, no entries in the journald log. I can’t even see the http request, even on log=“debug”.

Any idea what may cause this behaviour? Already tried to clear the browser cache, but no change unfortunately.

2

Hi @matthias, can you let me know if there are multiple namespaces or regions at play here? I’d like to help diagnose but want to narrow things down a bit.

3

Sure, happy for any support to fix this.

I’m running this in my homelab, so no enterprise subscription and no namespaces.

Just a single region, but I recently added a new datacenter to my setup. Earlier I was running three server nodes (DC "home), recently I added two client nodes (DC “dmz”).
Not sure if this is related, though.

Any logs or experimentations I should do?

BTW: Updated the CSI driver last weekend. It’s on v4.8.0 now, but the issue still persists.

4

I just wanted to chime in that I also see the same message:

Not Found
What you're looking for couldn't be found. It either doesn't exist or you are not authorized to see it.

It has been that way since I started using Nomad a few months ago, with version 1.8.1, I believe.

This is also a homelab. Nothing extravagant.
If you need any other information, please let me know.

Thanks

1 Like
5

Looking at the browser console, it appears URLs are being improperly encoded. I see a network request for https://[my.host.name]/v1/volume/csi%2Fmy-volume-name. Dumping that directly into the browser gives a 404, but if I decode the encoded slash between csi and my-volume-name (https://[my.host.name]/v1/volume/csi/my-volume-name), I get the JSON payload I assume the UI is looking for.

2 Likes
6

Can confirm that replacing the “%2F” with “/” resolves the 404.

@tgross Sorry to shamelessly ping you. Should I open a ticket, or will you do it internally?

7

This appears to have been fixed with this PR [ui] Volumes and plugins navigation fixes, generally by philrenaud · Pull Request #24542 · hashicorp/nomad · GitHub

1 Like