Comment 9 for bug 1878923

The issue actually isn't with storage it's with NUMA detection. As of MAAS 2.7 almost all commissioning data is coming from 50-maas-01-commissioning. If processing fails no data from that file is modeled. You have 4 NUMA nodes setup but only 2 have any memory assigned to them. MAAS is failing when it tries to convert 0 bytes to 0 megabytes. This is clearly a bug in MAAS that needs to be fixed but I'm wondering if this configuration was intentional? If so what is the use case?

    "memory": {
        "nodes": [
            {
                "numa_node": 0,
                "hugepages_used": 0,
                "hugepages_total": 0,
                "used": 1314131968,
                "total": 16814940160
            },
            {
                "numa_node": 1,
                "hugepages_used": 0,
                "hugepages_total": 0,
                "used": 0,
                "total": 0
            },
            {
                "numa_node": 2,
                "hugepages_used": 0,
                "hugepages_total": 0,
                "used": 753184768,
                "total": 16905523200
            },
            {
                "numa_node": 3,
                "hugepages_used": 0,
                "hugepages_total": 0,
                "used": 0,
                "total": 0
            }
        ],
        "hugepages_total": 0,
        "hugepages_used": 0,
        "hugepages_size": 2097152,
        "used": 602902528,
        "total": 33720463360
    },