Bug 617444

Summary: beaker selected a wrong system when specifying memory < 4G
Product: [Retired] Beaker Reporter: Han Pingtian <phan>
Component: schedulerAssignee: Bill Peck <bpeck>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 0.5CC: bpeck, dkovalsk, kbaker, mcsontos, rmancy
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-12 06:15:07 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:
Bug Depends On:    
Bug Blocks: 629211    

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