-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CSI volumes API doesn't respect wildcard namespace filter #11574
Comments
@dcarbone in the volume UI can you switch the namespace to default? For me the volumes which are in the default namespace only show there and not in "All (*)": |
@apollo13: ah, yep, that's it. Apologies, I noticed this under v1.2.1 and I suspect I was running into #11563 at the same time I was trying to load the UI. After upgrading to v1.2.2, I am able to see them when selecting the appropriate namespace. I quite stupidly only looked at "all" and assumed the same behavior. I'll update the issue accordingly, thanks! |
I took a quick look into this and it looks like this is arguably not a bug in the UI but in the RPC layer for not respecting the wildcard that we implemented for the job API. But the namespace switcher component expects it to be everywhere. I'm going to rename and retag the issue slightly so that it's assigned to the right folks to fix. Repro, on a dev agent running the hostpath demo:
|
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
Nomad v1.2.2 (78b8c171a211f967a8b297a88a7e844b3543f2b0)
Operating system and Environment details
Linux 5.11.0-1022-raspi aarch64
Issue
After upgrading servers to v1.2.0+, any / all csi volumes do not appear in the web UI. The volumes are present in the CLI output.
Reproduction steps
Expected Result
nomad volume status
Actual Result
Volumes created and registered successfully, but are only viewable in UI when filtering by their appropriate namespace. The "All" filter yields no results.
Nomad Server logs (if appropriate)
No relevant logging appears on the servers, no errors, etc.
The text was updated successfully, but these errors were encountered: