Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 647470

Summary:	[Beaker][Inventory] Unable to get correct memory value on host
Product:	[Retired] Beaker	Reporter:	Jeff Burke <jburke>
Component:	inventory	Assignee:	beaker-dev-list
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	0.5	CC:	bpeck, dcallagh, ebaak, ineilsen, mcsontos, tools-bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	Inventory
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-26 06:32:36 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jeff Burke 2010-10-28 14:06:14 UTC

Description of problem:
 HP had sent us some additional ram to use while doing some limits testing.
The host was bumped it up to 2TB in ram. Provision inventory distro was run. The ram was reflected in inventory properly.

 We have removed the RAM and the unit is now running with 64GB of ram. I tried running both the provision inventory distro and running the inventory task. 

bkr workflow-simple --task /distribution/inventory --machine hp-dl980g7-01.lab.bos.redhat.com --family RedHatEnterpriseLinuxServer5 --tag RELEASED --arch x86_64

https://beaker.engineering.redhat.com/view/hp-dl980g7-01.lab.bos.redhat.com

Currnetly the system shows 258061 MB

Comment 1 Jeff Burke 2013-02-06 13:40:21 UTC

I don't believe this is even valid any longer. I believe the current inventory works properly.

Thanks,
Jeff

Comment 2 Dan Callaghan 2013-02-06 22:32:53 UTC

There is still one issue with memory size reporting, which is that we only report the memory available to the kernel instead of the amount of physically installed memory, which is what people would generally expect. I think there is another bug open about that though...

Comment 4 Dan Callaghan 2015-08-26 06:32:36 UTC

This is effectively a dupe of bug 541294, which is now solved with the lshw migration in beaker-system-scan 2.0 / Beaker 21.0.

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