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

[ui] CSI Volume Listing has invalid Allocation Count #8362

Closed
cgbaker opened this issue Jul 5, 2020 · 2 comments · Fixed by #8590
Closed

[ui] CSI Volume Listing has invalid Allocation Count #8362

cgbaker opened this issue Jul 5, 2020 · 2 comments · Fixed by #8590
Assignees

Comments

@cgbaker
Copy link
Contributor

cgbaker commented Jul 5, 2020

Nomad version

Nomad 0.12.0-beta2

Issue

The # Allocs column in the CSI Volume Listing page (/ui/csi/volumes) is not correct:
Screen Shot 2020-07-05 at 3 54 46 PM
It is always zero. The network trace suggests this is being populated from GET /v1/volumes, which does not include the necessary allocations array in the list stub entries.

Reproduction steps

Create a CSI volume and use it from an allocation (reach out to me for a reproduction environment).

@cgbaker cgbaker added this to the 0.12.0 milestone Jul 5, 2020
@backspace
Copy link
Contributor

The UI is expecting GET /v1/volumes to have ReadAllocs and WriteAllocs which it then concatenates into the synthetic allocations computed property on a volume model, does the endpoint return those?

image

I have yet to use any of this with true volumes vs a mocked API but if the response does include the allocations it seems like it shouldn’t be too difficult to correct this.

@github-actions
Copy link

github-actions bot commented Nov 3, 2022

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 Nov 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants