Description of problem:
HP BL460c Gen9 has 512 gb ram which is ddr4.
When I execute:

  openstack baremetal introspection bulk start

That resulted in:

+------------------------+-------------------------------------------------------------------------+
| Property               | Value                                                                   |
+------------------------+-------------------------------------------------------------------------+
 ...
| properties             | {u'memory_mb': u'512', u'cpu_arch': u'x86_64', u'local_gb': u'278',     |
 ...
+------------------------+-------------------------------------------------------------------------+

"memory_mb" doesn't have to be 512, has to be 524288.

But if the target hardware having ddr3 ram, output was fine. Meaning is that unit is mb.

If I did this:

  ironic node-update <node> replace properties/memory_mb=524288

everything is fine.

What I've already checked are:

    python-ironicclient-0.5.1-9.el7ost.noarch
    python-ironic-discoverd-1.1.0-5.el7ost.noarch
    openstack-ironic-conductor-2015.1.0-9.el7ost.noarch
    openstack-ironic-api-2015.1.0-9.el7ost.noarch
    openstack-ironic-common-2015.1.0-9.el7ost.noarch
    openstack-ironic-discoverd-1.1.0-5.el7ost.noarch

But I could not find out any bugs.
I'm quite sure I've missed something -;

Version-Release number of selected component (if applicable):

    python-ironicclient-0.5.1-9.el7ost.noarch
    python-ironic-discoverd-1.1.0-5.el7ost.noarch
    openstack-ironic-conductor-2015.1.0-9.el7ost.noarch
    openstack-ironic-api-2015.1.0-9.el7ost.noarch
    openstack-ironic-common-2015.1.0-9.el7ost.noarch
    openstack-ironic-discoverd-1.1.0-5.el7ost.noarch

How reproducible:

Probably yes. If we have same hardware having.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: