MAAS detects 0 cores, RAM available for KVM host, reports negative availability on pod compose
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Alberto Donato | ||
2.9 |
Won't Fix
|
Undecided
|
Unassigned | ||
maas-ui |
Fix Released
|
Unknown
|
Bug Description
On MAAS 2.9.2, I have a KVM host with 32 cores and 64GiB of memory:
ubuntu@tyrogue:~$ cat /proc/cpuinfo | grep processor | wc -l
32
ubuntu@tyrogue:~$ free -h
total used free shared buff/cache available
Mem: 62Gi 23Gi 1.8Gi 148Mi 37Gi 38Gi
Swap: 0Gi 0Mi 0Gi
That is also being used as the MAAS controller. The controller page reports the correct information, 32 cores, 64 GiB of memory. However the KVM tab shows a different story:
18 of 0 allocated
55834574848 of 0 B allocated
240 of 490 GB allocated
This blocks the creation of additional VMs. Restarting the MAAS snap on this host does not restore functionality.
Related branches
- Björn Tillenius: Approve
- MAAS Lander: Approve
-
Diff: 124 lines (+50/-20)2 files modifiedsrc/maasserver/models/tests/test_virtualmachine.py (+27/-7)
src/maasserver/models/virtualmachine.py (+23/-13)
tags: | added: ui |
Changed in maas-ui: | |
importance: | Undecided → Unknown |
Changed in maas: | |
assignee: | nobody → Alberto Donato (ack) |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas-ui: | |
status: | New → Fix Released |
Changed in maas: | |
status: | Fix Committed → Fix Released |
sosreport