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

Bug 498346

Summary:	vm-gahp mishandling job's vm_memory
Product:	Red Hat Enterprise MRG	Reporter:	Matthew Farrellee <matt>
Component:	condor	Assignee:	Matthew Farrellee <matt>
Status:	CLOSED DUPLICATE	QA Contact:	MRG Quality Engineering <mrgqe-bugs>
Severity:	high	Docs Contact:
Priority:	high
Version:	1.1.1
Target Milestone:	1.2
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-05-01 15:45:25 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 Matthew Farrellee 2009-04-30 00:36:01 UTC

Description of problem:

condor_submit's manual page says vm_memory is in MiB, the VM_MEMORY configuration for the vm gahp says it is in MiB, and libvirt says that the <memory> element of the VM's <domain> is in KiB.

However, the vm-gahp was passing vm_memory through to libvirt without doing the MiB->KiB conversion.

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

condor before 7.3.1-0.3

How reproducible:

100%

Steps to Reproduce:
1. Treat the vm_memory as if it is MiB and notice the small memory size for a running domain with virsh
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Matthew Farrellee 2009-04-30 00:46:36 UTC

A workaround for versions of Condor with this bug is to treat both the vm_memory submit command and VM_MEMORY configuration as if they were in KiB. After the bug is fixed they need to be treated as MiB.

Comment 2 Matthew Farrellee 2009-05-01 15:45:25 UTC


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