UI is presenting wrong storage pool sizes in clusters
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Alexsander de Souza | ||
maas-ui |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
the UI is calculating storage pool sizes wrongly when CEPH pools are involved.
when shared pools are present in a cluster the UI should not stack their sizes, as every VMHost will report that pool but they all point to the same storage capacity.
the vmcluster endpoint has the correct pool sizes and aggregated storage capacity:
{
"name": "CEPH-LAB",
"project": "cluster-lab",
"id": 3,
"total": {
"cores": 2,
"memory": 4294967296,
},
"available": {
"cores": 2,
"memory": 4294967296,
},
"vm_count": 0,
"vmhost_count": 2,
"version": "4.19",
"storage_
"local": {
"free": 14555799552,
},
"remote": {
"free": 201853894656,
}
},
"used": {
"cores": 0,
"memory": 0,
},
"resource_uri": "/MAAS/
}
Related branches
- Christian Grabowski: Approve
- MAAS Lander: Approve
-
Diff: 195 lines (+52/-9)7 files modifiedsrc/maasserver/api/tests/test_vmcluster.py (+6/-0)
src/maasserver/api/vmcluster.py (+7/-1)
src/maasserver/models/tests/test_vmcluster.py (+6/-1)
src/maasserver/models/virtualmachine.py (+8/-2)
src/maasserver/models/vmcluster.py (+11/-4)
src/maasserver/websockets/handlers/tests/test_vmcluster.py (+8/-0)
src/maasserver/websockets/handlers/vmcluster.py (+6/-1)
Changed in maas: | |
assignee: | nobody → Alexsander de Souza (alexsander-souza) |
importance: | Undecided → Critical |
Changed in maas: | |
status: | New → In Progress |
Changed in maas: | |
milestone: | none → 3.1.0 |
status: | In Progress → Fix Committed |
Changed in maas: | |
milestone: | 3.1.0 → 3.1.0-beta5 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Just relaying what was said in Mattermost - we can switch over to using the vmcluster endpoint once it includes each pool's type and path.