Bug 472607 - Slot Type definitions only allow lowercase
Summary: Slot Type definitions only allow lowercase
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: grid
Version: 1.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: 1.1.1
: ---
Assignee: Robert Rati
QA Contact: Kim van der Riet
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-21 22:56 UTC by Robert Rati
Modified: 2009-04-21 16:19 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-04-21 16:19:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2009:0434 0 normal SHIPPED_LIVE Red Hat Enterprise MRG Messaging and Grid Version 1.1.1 2009-04-21 16:15:50 UTC

Description Robert Rati 2008-11-21 22:56:36 UTC
Description of problem:
The condor manual at http://www.cs.wisc.edu/condor/manual/v7.1/3_12Setting_Up.html#SECTION004127000000000000000

States that "The four attribute names are case insensitive when defining slot types.", however putting:

SLOT_TYPE_1 = CPUS=100%,DISK=100%,SWAP=100%

in condor's configuration file causes the startd to error with the message (in StartLog):

Unknown attribute "CPU=100%" in slot type 1

Changing the CPU to cpu causes a similar complaint about DISK.  setting them all to lowercase solves the issue.

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


How reproducible:


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


Expected results:


Additional info:

Comment 1 Robert Rati 2009-01-12 14:13:13 UTC
Slot type definitions can now be lower case.  The startd wasn't being case insensitive when it was checking the configuration files.  Added tolower() in switch statement for slot type definitions.

Comment 2 Jan Sarenik 2009-02-12 09:09:14 UTC
Excuse me, but I am unable to find a version of Condor
which would produce any log complaint about the mentioned
line. Should I use any special debugging option to catch it?

I have tried these versions:
  condor-7.0.4-4.el5.i386 (from MRG 1.0.1)
  condor-7.1.4-0.3.el5.i386
  condor-7.1.4-0.5.el5.i386
  condor-7.2.2-0.1.el5.i386

Comment 3 Robert Rati 2009-02-12 18:30:59 UTC
This was run into when testing dynamic provisioning.  If you add the following to the condor config file then you should see an error in StartLog:

SLOT_TYPE_1 = CPUS=100%,DISK=100%,SWAP=100%
SLOT_TYPE_1_PARTITIONABLE = TRUE
NUM_SLOTS = 1
NUM_SLOTS_TYPE_1 = 1

Comment 4 Jan Sarenik 2009-02-13 15:03:26 UTC
Can you please also write the version number on which you
experienced the bug, please?

From the date of message you wrote about adding tolower()
I guess the bug should be present in condor <= 7.2.0-3
Is this assumption right?

Comment 5 Jan Sarenik 2009-02-13 15:09:27 UTC
verified on condor-7.2.2-0.1.el5
reproduced on condor-7.1.4-0.3.el5

Comment 7 errata-xmlrpc 2009-04-21 16:19:01 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/RHEA-2009-0434.html


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