Bug 1281614

Summary: Wrong memory detected for discovered SuperMicro system
Product: Red Hat OpenStack Reporter: Thom Carlin <tcarlin>
Component: openstack-ironic-discoverdAssignee: RHOS Maint <rhos-maint>
Status: CLOSED WONTFIX QA Contact: Raviv Bar-Tal <rbartal>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.0 (Kilo)CC: apevec, dtantsur, lhh, lmartins, mburns, rhel-osp-director-maint, slinaber, tcarlin
Target Milestone: ---   
Target Release: 7.0 (Kilo)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-12 15:16:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Thom Carlin 2015-11-12 23:24:39 UTC
Description of problem:

If a Supermicro is chosen as a node for RHCS-I/Triple-O Node, the memory is incorrectly reported as MB instead of GB

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

1.1.0-7.el7ost

How reproducible:

100%

Steps to Reproduce:
1. Install RHCS-I 
2. Install Triple-O
3. In Deployment, register a Supermicro node

Actual results:

Memory: 32 MB

Expected results:

Memory: 32 GB

Additional info:

ironic-discoverd-ramdisk is using: 
dmidecode --type memory | grep Size | awk '{ print $2; }' | grep -E '[0-9]+'

This works for Dell because it assumes MB:
dmidecode --type memory | grep Size
	Size: 8192 MB
	Size: 8192 MB
	Size: 8192 MB
	Size: 8192 MB

but not so well for SuperMicro:
 dmidecode --type memory | grep Size
	Size: 32 GB
	Size: No Module Installed
	Size: No Module Installed
	Size: No Module Installed

Comment 2 Thom Carlin 2016-01-28 14:03:17 UTC
will propagate through to nova flavor-list

Comment 3 Thom Carlin 2016-01-28 15:49:13 UTC
Workaround: 
mysql
use ironic;
update nodes SET properties='<full properties with proper memory size>' where id=<node_id>;

Comment 4 Mike Burns 2016-04-07 20:57:01 UTC
This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.

Comment 6 Dmitry Tantsur 2016-07-08 12:44:36 UTC
Hi! What's the release version this bug is reported against? I'm pretty sure we got it fixed either in Mitaka (OSP9) or Newton (OSP10).

Comment 7 Thom Carlin 2016-07-08 12:45:37 UTC
Kilo (OSP7)

Comment 8 Dmitry Tantsur 2016-07-08 15:13:11 UTC
Thanks, fixing the flags and the project then.

Comment 9 Dmitry Tantsur 2016-12-12 15:16:39 UTC
Hi! I'm sorry, but the OSP7 version has diverged so much from the current code, and is so difficult to update in a safe fashion, that we decided not to fix this bug. Please update nodes' memory_mb manually as a workaround. Thanks for understanding!