Bug 159 - features not supported with procs
: features not supported with procs
Status: NEW
Product: TORQUE
libtorque
: 2.5.x
: PC Linux
: P5 major
Assigned To: David Beer
:
:
:
  Show dependency treegraph
 
Reported: 2011-10-02 16:19 MDT by Martin Siegert
Modified: 2011-10-03 10:35 MDT (History)
2 users (show)

See Also:


Attachments


Note

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


Description Martin Siegert 2011-10-02 16:19:51 MDT
We now have two different processors in the cluster and introduced a
corresponding feature in the server_priv/nodes file:

b1 np=8 e5430
b2 np=8 e5430
...
b161 np=12 x5650
b161 np=12 x5650
...

and configured moab (via nodesets) such that a job can only run on nodes that
have either the feature e5430 or x5650.

When I now submit a job with -l procs=1:x5650 or -l procs=1:e5430 qsub returns:

qsub: Illegal attribute or resource value for  Resource_List.procs

The error comes from attr_fn_l.c:143:

Breakpoint 29, decode_l (patr=0xb8671b0, name=0xb86a1e8 "Resource_List", 
    rescn=0xb86a1f6 "procs", val=0xb86a1fc "1:e5430") at attr_fn_l.c:143
143             return (PBSE_BADATVAL);  /* invalid string */

Unfortunately this is a complete showstopper for us.

- Martin
Comment 1 Ken Nielson 2011-10-03 10:20:38 MDT
This works as designed. procs was not designed to work with any additional
properties or features
Comment 2 Martin Siegert 2011-10-03 10:35:36 MDT
You are basically saying that this is a design flaw. Doesn't mean that it
should not get fixed. It is incomprehensible to users that they can specify a
feature (like a processor architecture) when using "nodes", but not when using
"procs".