[Bug 1752440] Re: Lshw incorrectly detects amount of RAM in system

[Douglas]

I tried deploying Bionic out through MaaS but it doesn't seem to be
working. Looking at the console of the system, I'm getting a "failed
posting event: start: init-local/check-cache: attempting to read from
cache [trust]". Screenshot is attached as well (let me know if you want
me to open up a separate ticket for this). Since I can't deploy out
Bionic, I'll try compiling lshw from scratch.

** Attachment added: "maas18.04deploy.png"
   https://bugs.launchpad.net/maas/+bug/1752440/+attachment/5067453/+files/maas18.04deploy.png

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to lshw in Ubuntu.
https://bugs.launchpad.net/bugs/1752440

Title:
  Lshw incorrectly detects amount of RAM in system

Status in MAAS:
  Triaged
Status in lshw package in Ubuntu:
  Incomplete

Bug description:
  When commissioning our new servers, we are only seeing 50% of the
  memory show up in the MaasUI. Looking at lshw, it looks like only 12
  of the 24 DIMMs are listed (we see 384GB but we have 768GB).
  Everything else seems to be fine, number of cores, disks, etc... When
  running free on the machine, we get the expected amount of RAM (768GB)

  Current:
  384GB

  Expecting
  768GB

  root at maas:~# dpkg -l '*maas*'
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name                    Version          Architecture     Description
  +++-=======================-================-================-===================================================
  ii  maas                    2.3.0-6434-gd354 all              "Metal as a Service" is a physical cloud and IPAM
  ii  maas-cli                2.3.0-6434-gd354 all              MAAS client and command-line interface
  un  maas-cluster-controller <none>           <none>           (no description available)
  ii  maas-common             2.3.0-6434-gd354 all              MAAS server common files
  ii  maas-dhcp               2.3.0-6434-gd354 all              MAAS DHCP server
  ii  maas-dns                2.3.0-6434-gd354 all              MAAS DNS server
  ii  maas-proxy              2.3.0-6434-gd354 all              MAAS Caching Proxy
  ii  maas-rack-controller    2.3.0-6434-gd354 all              Rack Controller for MAAS
  ii  maas-region-api         2.3.0-6434-gd354 all              Region controller API service for MAAS
  ii  maas-region-controller  2.3.0-6434-gd354 all              Region Controller for MAAS
  un  maas-region-controller- <none>           <none>           (no description available)
  un  python-django-maas      <none>           <none>           (no description available)
  un  python-maas-client      <none>           <none>           (no description available)
  un  python-maas-provisionin <none>           <none>           (no description available)
  ii  python3-django-maas     2.3.0-6434-gd354 all              MAAS server Django web framework (Python 3)
  ii  python3-maas-client     2.3.0-6434-gd354 all              MAAS python API client (Python 3)
  ii  python3-maas-provisioni 2.3.0-6434-gd354 all              MAAS server provisioning libraries (Python 3)

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1752440/+subscriptions