Bug 708172 - Memory value doesn't change after Inventory job is run
Summary: Memory value doesn't change after Inventory job is run
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: inventory
Version: 0.6
Hardware: Unspecified
OS: Linux
unspecified
low vote
Target Milestone: ---
Assignee: Dan Callaghan
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-26 21:07 UTC by Paul Baumgardner
Modified: 2019-05-22 13:39 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-16 00:51:52 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Paul Baumgardner 2011-05-26 21:07:17 UTC 
Description of problem:

Changed memory in a system from 4GB to 1GB:
https://beaker-stage.app.eng.bos.redhat.com/view/dev-kvm-guest-01.rhts.eng.bos.redhat.com

Reran Inventory job.

The memory listed on the Details page for the system is different (it did not change) than what is listed on the Key/Values tab.


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


How reproducible:

Always

Steps to Reproduce:
1.  Change memory in system
2.  Run Inventory job
3.  Check memory on Detail tab vs. Key Value tab
  
Actual results:

Memory amount listed is different

Expected results:

Memory amount should be the same


Additional info:
Comment 1 wang jiabo 2011-06-10 02:39:00 UTC 
I also met the issue,
could you tell me when we can fix the bug
our customers still complain he found a wrong mem info in beaker,
thanks
Comment 2 Dan Callaghan 2011-06-10 02:42:39 UTC 
(In reply to comment #1)

This will be fixed in Beaker 0.6.13, which is scheduled for release next Thursday.
Note You need to log in before you can comment on or make changes to this bug.