Bug 472837

Summary:	Dynamic Provisioning - Problems specifying disk usage
Product:	Red Hat Enterprise MRG	Reporter:	Robert Rati <rrati>
Component:	grid	Assignee:	Matthew Farrellee <matt>
Status:	CLOSED ERRATA	QA Contact:	Kim van der Riet <kim.vdriet>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.0
Target Milestone:	1.1
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-02-04 16:05:44 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 Robert Rati 2008-11-24 23:19:17 UTC

Description of problem:
Submitting:
universe = vanilla
executable = /bin/sleep
arguments = 3m
transfer_executable = false
should_transfer_files = if_needed
when_to_transfer_output = on_exit
notification = error
getenv = false
requirements = Machine == "north-13.lab.bos.redhat.com"
request_disk = 44446845
priority = 100
queue 10

Won't run.  When looking at STartLog with D_JOB and D_MACHINE, I see:
<only relevant info>
REQ_CLASSAD: RequestDisk = 44446845
MACHINE_CLASSAD:Disk = 44446744

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


How reproducible:


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


Expected results:


Additional info:

Comment 1 Matthew Farrellee 2008-11-25 01:04:29 UTC

Issue was a lack of ceil() when calculating disk %.

A more complete solution would be to allow disk=# (instead of a faction or %) when creating slots.

This is fixed in 7.2.0-0.5

Comment 2 Robert Rati 2008-11-25 02:01:06 UTC

TotalDisk = 138896076

Comment 3 Robert Rati 2008-11-25 15:25:37 UTC

Jobs are now scheduled correctly when disk constraints are used.

Comment 5 errata-xmlrpc 2009-02-04 16:05:44 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-0036.html