Skip to content
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

Wildcard Namespace selector (namespace='*') for CSI Volumes does not return any results #11200

Closed
RickyGrassmuck opened this issue Sep 17, 2021 · 2 comments
Labels

Comments

@RickyGrassmuck
Copy link
Contributor

RickyGrassmuck commented Sep 17, 2021

Nomad version

 ➜  nomad version                    
Nomad v1.1.4 (acd3d7889328ad1df2895eb714e2cbe3dd9c6d82)

Operating system and Environment details

 ➜ awk -F'=' '/PRETTY_NAME/ {print $2}' /etc/os-release 
"Ubuntu 20.04.3 LTS"

Issue

The wildcard namespace selector ('*') does not list CSI volumes from all namespaces. It appears to be treating it as a specific namespace as it doesn't return any volumes from any namespace (including the default). This happens both in the Nomad UI as well as from the command line.

 ➜ nomad volume status -namespace=default
Container Storage Interface
ID                   Name                 Plugin ID   Schedulable  Access Mode
metrics_prometheus   metrics_prometheus   cinder-csi  true         single-node-writer
tf_registry          tf_registry          cinder-csi  true         single-node-writer
tf_registry_mongodb  tf_registry_mongodb  cinder-csi  true         single-node-writer
➜ nomad volume status -namespace=awesomes
Container Storage Interface
ID                Name              Plugin ID   Schedulable  Access Mode
metrics_influxdb  metrics_influxdb  cinder-csi  true         single-node-writer
 ➜ nomad volume status -namespace='*'
Container Storage Interface
No CSI volumes

Reproduction steps

  1. Spin up a Nomad Server and Client (With ACL's enabled, have not tested without ACL's).
  2. Create an additional Namespace
  3. Deploy a CSI plugin
  4. Create 2 CSI volumes, one in the default namespace and the other in the created namespace.
  5. Run the nomad volume status command specifying each namespace separately and notice the volumes appear as expected.
  6. Run the nomad volume status -namespace='*' command and see that it returns that there are no volumes.

Expected Result

The nomad volume status -namespace='*' command should output all volumes from all namespaces

Actual Result

The nomad volume status -namespace='*' does not return any volumes

Job file (if appropriate)

Nomad Server logs (if appropriate)

Can provide upon request

Nomad Client logs (if appropriate)

N/A

Nomad UI Screenshots

default-namespace
non-default-namespace
wildcard-ui

@lgfa29
Copy link
Contributor

lgfa29 commented Sep 17, 2021

Hi @rigrassm, thanks for the detailed report.

This is a known missing feature of the API. The original work to add the * namespace was focused on jobs and allocations. #7341 is the issue that involves adding this operator to other endpoints as well. Once this option is available via the API, the UI and CLI can start levering it.

I will close this one to keep the discussion there. Feel free to 👍 that issue or let us know if there's anything missing.

@github-actions
Copy link

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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants