Bug 559071 – VM_MEMORY handled inconsistently between Startd and VMGahp

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 559071 - VM_MEMORY handled inconsistently between Startd and VMGahp

Summary:	VM_MEMORY handled inconsistently between Startd and VMGahp

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise MRG
Classification:	Red Hat
Component:	condor (Show other bugs)
Sub Component:
Version:	1.2
Hardware:	All Linux

Priority	low Severity medium
Target Milestone:	1.3
Target Release:	---
Assigned To:	Matthew Farrellee
QA Contact:	Luigi Toscano
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2010-01-26 22:59 EST by Matthew Farrellee
Modified:	2010-10-14 11:57 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2010-10-14 11:57:45 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

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

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2010:0773	normal	SHIPPED_LIVE	Moderate: Red Hat Enterprise MRG Messaging and Grid Version 1.3	2010-10-14 11:56:44 EDT

Groups: None (edit)

Description Matthew Farrellee 2010-01-26 22:59:24 EST

condor through 7.4.2-0.5

http://condor-wiki.cs.wisc.edu/index.cgi/tktview?tn=1143

 condor_startd.V6/vmuniverse_mgr.cpp:	vmtmp = param( "VM_MEMORY" );
 condor_vm-gahp/vmgahp_config.cpp:	int tmp_config_value = param_integer("VM_MEMORY", 0);

VM_MEMORY is not evaluated when param'd by the Startd, which means VM_MEMORY = 1 + 1 is different when looked up in the vm-gahp vs the startd. Both should use param_integer.

Issue:

VM_MEMORY = 2005 * 4

condor_status -vm reports only 2005 memory and StartLog shows:

01/26 22:33:05 ........VMGAHP info........
VM_GAHP_VERSION = "0.0.1"
VM_Type = "kvm"
VM_Memory = 8020
VM_Networking = TRUE
VM_Networking_Types = "nat,bridge"
01/26 22:33:05 
01/26 22:33:05 VMType('kvm') is supported
01/26 22:33:05 The maximum available memory for vm universe is set to 2005 MB

Expected to see 8020 in status -vm and the max avail memory message.

Comment 1 Matthew Farrellee 2010-01-26 23:01:40 EST

Expected (likely in 7.4.2-0.6)

01/26 23:00:34 ........VMGAHP info........
VM_GAHP_VERSION = "0.0.1"
VM_Type = "kvm"
VM_Memory = 8020
VM_Networking = TRUE
VM_Networking_Types = "nat,bridge"
01/26 23:00:34 
01/26 23:00:34 VMType('kvm') is supported
01/26 23:00:34 The maximum available memory for vm universe is set to 8020 MB

$ condor_status -vm
...
slot1@localhost  kvm    nat,bridge Unclaimed Idle     0.710  8020  0+00:00:04
...

Comment 2 Luigi Toscano 2010-04-16 12:37:21 EDT

The correct memory size is reported.
Tested on RHEL 5.5/Xen i386 & x86_64, RHEL 5.5/KVM x86_64.
condor-vm-gahp-7.4.3-0.8.el5
condor-7.4.3-0.8.el5
Moving to VERIFIED.

Comment 4 errata-xmlrpc 2010-10-14 11:57:45 EDT

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/RHSA-2010-0773.html

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