Bug 1259656 - Wrong unit of memory_mb output of hardware introspection.
Summary: Wrong unit of memory_mb output of hardware introspection.
Keywords:
Status: CLOSED DUPLICATE of bug 1256421
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-ironic
Version: 6.0 (Juno)
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: z6
: 8.0 (Liberty)
Assignee: Lucas Alvares Gomes
QA Contact: Toure Dunnon
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-03 09:50 UTC by Shinobu KINJO
Modified: 2019-08-15 05:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-03 11:56:41 UTC


Attachments (Terms of Use)

Description Shinobu KINJO 2015-09-03 09:50:33 UTC
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:

Comment 3 Mike Burns 2015-09-03 11:56:41 UTC

*** This bug has been marked as a duplicate of bug 1256421 ***


Note You need to log in before you can comment on or make changes to this bug.