[2.x] MAAS does not detect RAM in newly commissioned VMWARE VM's
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Medium
|
Unassigned |
Bug Description
This bug is very similar to a few that date back to 2012.
Basically the new VM's register and can be commissioned just fine, only when the ready state is reached the total RAM is valued at '0'.
CPU's and storage are detected just fine.
The major downside of this is that this halts my experimentation with openstack since Juju can't find any ready machines with a memory requirement of 3584 Megs (ServerError: 409 CONFLICT (No available machine matches constraints: mem=3584.0 zone=default))
I would be very happy with a workaround that will allow me to go forward with the openstack installation and at the same time help me understand the data structure of MAAS commissioned machines (I'm still looking at how to rename them)
dpkg -l '*maas*'|cat
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii maas 2.1.3+bzr5573-
ii maas-cli 2.1.3+bzr5573-
un maas-cluster-
ii maas-common 2.1.3+bzr5573-
ii maas-dhcp 2.1.3+bzr5573-
ii maas-dns 2.1.3+bzr5573-
ii maas-proxy 2.1.3+bzr5573-
ii maas-rack-
ii maas-region-api 2.1.3+bzr5573-
ii maas-region-
un maas-region-
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-
ii python3-django-maas 2.1.3+bzr5573-
ii python3-maas-client 2.1.3+bzr5573-
ii python3-
Changed in maas: | |
milestone: | none → 2.3.0 |
summary: |
- MAAS does not detect RAM in newly commissioned VMWARE VM's + [2.3] MAAS does not detect RAM in newly commissioned VMWARE VM's |
summary: |
- [2.3] MAAS does not detect RAM in newly commissioned VMWARE VM's + [2.x] MAAS does not detect RAM in newly commissioned VMWARE VM's |
Changed in maas: | |
status: | Incomplete → Triaged |
importance: | Undecided → Medium |
Changed in maas: | |
milestone: | 2.3.0 → 2.3.x |
>In addition:
description: System Memory
descripti on: DIMM Synchronous 2133 MHz (0.5 ns)
product: M393A2G40DB0-CPB
vendor: 00CE04B300CE
physical id: 0
serial: 40AD3081
descripti on: DIMM Synchronous 2133 MHz (0.5 ns)
product: M393A2G40DB0-CPB
vendor: 00CE04B300CE
physical id: 1
serial: 40AD308A
descripti on: DIMM Synchronous 2133 MHz (0.5 ns)
product: M393A2G40DB0-CPB
vendor: 00CE04B300CE
physical id: 2
serial: 40AD30A2
descripti on: DIMM Synchronous 2133 MHz (0.5 ns)
product: M393A2G40DB0-CPB
vendor: 00CE04B300CE
physical id: 3
serial: 40AD30A1
>lshw output excerpt from hardware node RAM that IS correctly detected by MAAS
>
*-memory
physical id: 1000
slot: System board or motherboard
size: 128GiB
*-bank:0
slot: A1
size: 16GiB
width: 64 bits
clock: 2133MHz (0.5ns)
*-bank:1
slot: A2
size: 16GiB
width: 64 bits
clock: 2133MHz (0.5ns)
*-bank:2
slot: A3
size: 16GiB
width: 64 bits
clock: 2133MHz (0.5ns)
*-bank:3
slot: A4
size: 16GiB
width: 64 bits
clock: 2133MHz (0.5ns)
>
description: System Memory
descripti on: DIMM DRAM EDO
physical id: 0
descripti on: DIMM DRAM [empty]
physical id: 0
descripti on: DIMM DRAM [empty]
physical id: 0
>and lshw output excerpt from VMWare ESX 6.5 node RAM that is not correctly detected by MAAS.
>
*-memory:0
physical id: 28
slot: System board or motherboard
capacity: 1GiB
*-memory:1 UNCLAIMED
physical id: 1
*-bank UNCLAIMED
slot: RAM slot #0
size: 8GiB
width: 32 bits
*-memory:2 UNCLAIMED
physical id: 2
*-bank UNCLAIMED
slot: RAM slot #1
*-memory:3 UNCLAIMED
physical id: 3
*-bank UNCLAIMED
slot: RAM slot #2