You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The # Allocs column in the CSI Volume Listing page (/ui/csi/volumes) is not correct:
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).
The text was updated successfully, but these errors were encountered:
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?
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.
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.
Nomad version
Nomad 0.12.0-beta2
Issue
The
![Screen Shot 2020-07-05 at 3 54 46 PM](https://user-images.githubusercontent.com/1675087/86542097-f1ab4180-bed7-11ea-9465-9aab4f86ae12.png)
# Allocs
column in the CSI Volume Listing page (/ui/csi/volumes
) is not correct:It is always zero. The network trace suggests this is being populated from
GET /v1/volumes
, which does not include the necessaryallocations
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).
The text was updated successfully, but these errors were encountered: