MaaS fails to over-commit resources correctly on VIRSH KVM hosts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Triaged
|
Medium
|
Unassigned |
Bug Description
I'm using snap version/build 3.2.0-11989-
I deployed a libvirt KVM (not LXD) host using MAAS on both a Dell r710 and a Dell r630. In both cases, the physical node deployed successfully (Ubuntu 20.04 - hwe-20.04 kernel). When I issue an over-commit, regardless of the size, the GUI reports correctly but the CLI shows no difference. Also, and it might be related, if I create a VM on this host, the commissioning fails. Previously, we were using MaaS 2.9 (I don't have the exact build, sorry), but libvirt worked perfectly fine.
For example, Dell r710, physically has 16 cores with 144GB RAM.
Steps to reproduce:
1. Confirm that a server is discovered and in the ready state.
2. Select the Deploy option, OS: Ubuntu, Release: Ubuntu 20.04 LTS "Focal Fossa", Kernel: focal (hwe-20.04), select the 'Register as MAAS KVM host' and select the 'libvirt' option.
3. Start deployment for machine.
4. Update CPU & Memory Overcommit (see screenshot png)
5. Log into CLI and issue `pods read` command.
6. CLI available resources are unchanged:
``` {
"name": "R1-710-26",
],
"zone": {
"name": "default",
"id": 1,
},
],
"total": {
},
"id": 42,
{
}
],
"tags": [
],
},
"used": {
},
"host": {
},
"version": "6.0.0",
"pool": {
"name": "virtual_
"id": 1,
},
"type": "virsh",
}
```
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Medium |
This shows what is available via GUI.