Comment 4 for bug 2018590

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`