LXD pod.total.local_storage refers to host
Bug #1878117 reported by
Caleb Ellis
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Lee Trager | ||
Bug Description
Pod objects returned from the websocket have helper fields for total/used/
This is easily fixed in the UI just by summing the storage pool data manually, but it would be good if the websocket returned the "actual" pod total/available storage instead of the host total/available storage.
Related branches
~ltrager/maas:lp1878117
- Alberto Donato (community): Approve
- MAAS Lander: Approve
-
Diff: 130 lines (+20/-14)5 files modifiedsrc/maasserver/models/bmc.py (+0/-3)
src/maasserver/models/tests/test_bmc.py (+0/-1)
src/metadataserver/builtin_scripts/tests/test_hooks.py (+0/-1)
src/provisioningserver/drivers/pod/lxd.py (+16/-5)
src/provisioningserver/drivers/pod/tests/test_lxd.py (+4/-4)
Revision history for this message
| Caleb Ellis (caleb-ellis) wrote | #1 |
| Changed in maas: | |
| status: | New → In Progress |
| importance: | Undecided → High |
| milestone: | none → 2.8.0rc1 |
| assignee: | nobody → Lee Trager (ltrager) |
Revision history for this message
| Lee Trager (ltrager) wrote | #2 |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Thanks for finding this. It looks like the issue is LXD composed machines are not linking block devices to the storage pool they use.