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:
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.
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
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
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?
verified on condor-7.2.2-0.1.el5 reproduced on condor-7.1.4-0.3.el5
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