[pod, wishlist] Add support for multiple storage pools.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Wishlist
|
Newell Jensen |
Bug Description
I have configured a Pod using Virsh and it is only showing a Local storage (118.9 GiB) however I use a ZFS pool that is 14TB.
virsh pool-list
Name State Autostart
-------
default active no
zfspool active yes
virsh pool-info default
Name: default
UUID: a33198cd-
State: running
Persistent: yes
Autostart: no
Capacity: 102.61 GiB
Allocation: 22.17 GiB
Available: 80.45 GiB
virsh pool-info zfspool
Name: zfspool
UUID: f64a089b-
State: running
Persistent: yes
Autostart: yes
Capacity: 16.25 TiB
Allocation: 9.48 GiB
Available: 16.24 TiB
maas maas pod read 1
Success.
Machine-readable output follows:
{
"total": {
"cores": 24,
"memory": 128907
},
"resource_uri": "/MAAS/
"name": "iaasdev",
"capabilities": [
],
"type": "virsh",
"available": {
"cores": 24,
"memory": 128907
},
"used": {
"cores": 0,
"memory": 0
},
"architectu
],
"id": 1
}
Related branches
- Blake Rouse (community): Approve
- MAAS Lander: Approve
-
Diff: 214 lines (+67/-30)2 files modifiedsrc/provisioningserver/drivers/pod/tests/test_virsh.py (+35/-9)
src/provisioningserver/drivers/pod/virsh.py (+32/-21)
Changed in maas: | |
importance: | Undecided → Wishlist |
status: | Incomplete → Triaged |
milestone: | none → next |
summary: |
- Virsh Pods are not detecting all storage pools + [pod, wishlist] Add support for multiple storage pools. |
Changed in maas: | |
milestone: | next → 2.4.0beta2 |
assignee: | nobody → Newell Jensen (newell-jensen) |
Changed in maas: | |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Actually, looking at this, this seems a lot like bug #1687305 — can you confirm you are using latest MAAS (or at least 2.2.1 which includes the fix)?
Local storage is reported as 127624953200 bytes, or 118.8599 GiB: MAAS misinterpreted storage size and assumed everything to be in GiB previously, so your 16.25TiB disk was added up as 16.25 GiB on top of 102.61 giving a total of 118.86Gib.
There seems to be another problem in that we are not ignoring inactive pools.
Can you please confirm what version of MAAS are you running?