hardware sync partially updates new machine specs (cpu and ram)

Bug #2018590 reported by Pablo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Triaged
High
Unassigned
3.3
Triaged
High
Unassigned
3.4
Triaged
High
Unassigned

Bug Description

I have added a VM to MAAS with 2cpus and 2GB ram. During the deployment step I enable the "hardware sync" option. Once the machine is deployed the hardware specs are correct in the maas webui but if I resize the VM by adding extra cpus and ram the maas webui doesn't show the correct amount for cpus/ram.

In screenshot 1 you can see the maas webui shows 2cpus/2GB ram in the main section (top) and in the numa section (bottom)

In screenshot 2, after the VM has been resized, the maas webui shows 4cpus/4G ram in the numa section (bottom) but still shows the wrong cpu/ram 2cpus/2GB ram in the main section (top)

I have tested it with MAAS 3.3.2 deployed as a snap.

Revision history for this message
Pablo (pescobar001) wrote :
Revision history for this message
Pablo (pescobar001) wrote :
Revision history for this message
Pablo (pescobar001) wrote :

Just to clarify, the machine is a VM but the OS has been deployed using a regular pxe boot. It's not a VM running in a kvm/lxd host managed by MAAS. The VM is running in a external hypervisor (proxmox)

Revision history for this message
Anton Troyanov (troyanov) wrote :

Hello Pablo,

Thank you for spotting this issue, it is indeed a bug and I was able reproduce it.

---
FTR, this is not UI issue, websocket API returns incorrect data:

```
"cpu_count": 2,
"cpu_speed": 2300,
"memory": 4.0,
```

Numa node returned is correct:
```
"numa_nodes": [
    {
        "id": 4,
        "index": 0,
        "memory": 6144,
        "cores": [
            0,
            1
        ],
        "hugepages_set": [
            {
                "page_size": 2097152,
                "total": 0
            }
        ]
    }
],
```

Output of machine resources binary:
```
"memory": {
    "nodes": [
        {
            "numa_node": 0,
            "hugepages_used": 0,
            "hugepages_total": 0,
            "used": 563499008,
            "total": 6442450944
        }
    ],
    "hugepages_total": 0,
    "hugepages_used": 0,
    "hugepages_size": 2097152,
    "used": 456855552,
    "total": 6442450944
},
```

It seems there is a bug in `_process_lxd_resources` at `maas/src/metadataserver/builtin_scripts/hooks.py:599`

Changed in maas:
status: New → Triaged
importance: Undecided → High
milestone: none → 3.4.0
Changed in maas:
milestone: 3.4.0 → 3.5.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.