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?
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-commissionin g. 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": {
"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,
"nodes": [
{
},
{
},
{
},
{
}
],
"used": 602902528,
"total": 33720463360
},