Hide Forgot
Description of problem: Discovery ramdisk detects _possible_ amount of RAM, not actual one. It was fixed in Git master by commit https://github.com/rdo-management/instack-undercloud/commit/9327553ecbbb7cc20bf32dd940bb32d02edb5b94 and in DIB ramdisk by patch https://review.openstack.org/#/c/156173/. How reproducible: on bare metal machines with RAM != maximum RAM Steps to Reproduce: 1. go through discovery on such a machine 2. Node.extra[memory_mb] in Ironic will be updated with wrong value
Fixed in stable/juno branch of instack-undercloud as commit https://github.com/rdo-management/instack-undercloud/commit/02853ff37851736d0aecdda3d30afe94db35b782
Verified: Environment: openstack-ironic-common-2015.1.0-4.el7ost.noarch openstack-ironic-discoverd-1.1.0-3.el7ost.noarch python-ironic-discoverd-1.1.0-3.el7ost.noarch python-ironicclient-0.5.1-5.el7ost.noarch openstack-ironic-conductor-2015.1.0-4.el7ost.noarch openstack-ironic-api-2015.1.0-4.el7ost.noarch instack-undercloud-2.1.2-1.el7ost.noarch The machine has 48GB of ram. After the discovery, running "ironic node-show <id>": {u'memory_mb': u'49152'
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2015:1549