Bug 1256421 - Incorrect RAM report
Summary: Incorrect RAM report
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-ironic-discoverd
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: async
: 7.0 (Kilo)
Assignee: Dmitry Tantsur
QA Contact: Omri Hochman
URL:
Whiteboard:
: 1255733 1258647 1259656 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-24 14:25 UTC by Alessandro Vozza
Modified: 2019-08-15 05:12 UTC (History)
18 users (show)

Fixed In Version: openstack-ironic-discoverd-1.1.0-7.el7ost
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-22 19:44:58 UTC


Attachments (Terms of Use)
ironic report (42.34 KB, text/plain)
2015-08-24 14:25 UTC, Alessandro Vozza
no flags Details


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1929 normal SHIPPED_LIVE Important: openstack-ironic-discoverd security update 2015-10-22 23:44:50 UTC
Red Hat Knowledge Base (Solution) 1603903 None None None 2016-01-27 22:10:52 UTC

Description Alessandro Vozza 2015-08-24 14:25:17 UTC
Created attachment 1066407 [details]
ironic report

Description of problem:

After the benchmark of some nodes the memory_mb is set to 512 MB instead of 512GB.

[stack@pvn0014 ~]$ openstack baremetal show 4f16afcf-5b57-4676-96b9-46d603552dab | grep properties
| properties             | {u'memory_mb': u'512', u'cpu_arch': u'x86_64', u'local_gb': u'118', u'cpus': u'48', u'capabilities': u'boot_option:local'}

Where are you experiencing the behavior?  What environment?

Expected to see a long number 528089 or something. I think this will cause issues when assigning flavors that have larger memory then 512mb.
Node has available:
[root@NODE~]# free -m
              total        used        free      shared  buff/cache   available
Mem:         515712        3512      315631         828      196568      510890
Swap:          1023           0        1023

Attaching the extra_hardware-4f16afcf-5b57-4676-96b9-46d603552dab from swift

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 4 Mike Burns 2015-08-31 23:26:59 UTC
*** Bug 1258647 has been marked as a duplicate of this bug. ***

Comment 5 Mike Burns 2015-09-03 11:56:41 UTC
*** Bug 1259656 has been marked as a duplicate of this bug. ***

Comment 6 Mike Burns 2015-10-05 12:51:49 UTC
*** Bug 1255733 has been marked as a duplicate of this bug. ***

Comment 9 Omri Hochman 2015-10-22 17:27:01 UTC
Unable to reproduce with : 
---------------------------
python-ironic-discoverd-1.1.0-8.el7ost.noarch
openstack-ironic-discoverd-1.1.0-8.el7ost.noarch

-----------------------------------------------------
(1) 'openstack baremetal show' 5ab81320-55bb-409e-aa27-c1ad37db50b4 | grep properties

does not have properties at all .. 

(2) ironic node-show shows exact data : 

[stack@rhos-compute-node-18 ~]$ ironic node-show 9d00a66d-cdf6-481e-b1d1-4107c4380131 | grep properties
| properties             | {u'memory_mb': u'24576', u'cpu_arch': u'x86_64', u'local_gb': u'464',    |

[root@overcloud-cephstorage-0 ~]# free -m
              total        used        free      shared  buff/cache   available
Mem:          48091         545       47060           0         485       47294
Swap:             0           0           0

Comment 10 Omri Hochman 2015-10-22 17:29:27 UTC
Correcting my mistake from the previous comment ( it was different host): 


[stack@rhos-compute-node-18 ~]$ ironic node-show e6a17b16-f267-466b-9769-a4767cb259c8 | grep propertie
| properties             | {u'memory_mb': u'49152', u'cpu_arch': u'x86_64', u'local_gb': u'49',     |

[root@overcloud-cephstorage-0 ~]# free -m
              total        used        free      shared  buff/cache   available
Mem:          48091         545       47060           0         485       47294
Swap:             0           0           0

Comment 12 errata-xmlrpc 2015-10-22 19:44:58 UTC
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/RHSA-2015:1929


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