Bug 617444 - beaker selected a wrong system when specifying memory < 4G
Summary: beaker selected a wrong system when specifying memory < 4G
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: scheduler
Version: 0.5
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Bill Peck
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 629211
TreeView+ depends on / blocked
 
Reported: 2010-07-23 03:44 UTC by Han Pingtian
Modified: 2011-09-28 15:34 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-08-12 06:15:07 UTC
Embargoed:


Attachments (Terms of Use)

Description Han Pingtian 2010-07-23 03:44:36 UTC
Description of problem:
I have two recipes, which specify to select systems with memory < 4G. But Beaker selected two system which both has 4G memory:

https://beaker.engineering.redhat.com/recipes/14897
https://beaker.engineering.redhat.com/recipes/14899

I would like Beaker can select system which has memory really less than 4G.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Han Pingtian 2010-07-23 03:57:50 UTC
It likes like in rhts, it always can select the correct system:

https://rhts.redhat.com/cgi-bin/rhts/jobs.cgi?id=167727

So, maybe this is a regression of beaker.

Comment 2 Raymond Mancy 2010-07-28 05:57:22 UTC
From what I can see the only place we show the memory is in the Key/Value.
I think there could be some a discrepancies between it and the memory value in the system table.

I did some testing on stage and found this to be the case.

I'm waiting to get a sysadmin to query the DB for me, and for the machines to be free so I can check discrepancies myself.

In the meantime I'll add a field into the details which shows the memory as it is in the system table


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