Bug 5272 - Invalid parsing of RSL file
: Invalid parsing of RSL file
Status: RESOLVED LATER
: GRAM
gt2 Gatekeeper/Jobmanager
: 4.0.3
: All Linux
: P5 normal
: ---
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2007-05-07 03:39 by
Modified: 2012-09-12 13:20 (History)


Attachments


Note

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


Description From 2007-05-07 03:39:51
If we specify "count=2:" in RSL file, "globusrsl -d" cannot identify that count
is invalid. This bug causes that LRM gives us error instead of GRAM/Gatekeeper.
For example I submit the following RSL script and get error.

-------------------Error from OpenPBS---------------------------
/var/spool/torque/mom_priv/jobs/132.server..SC: line 55: test: 2:: integer
expression expected

---------------------RSL script---------------------------------
+
( &(resourceManagerContact="Server.eng4.shirazu.ac.ir/jobmanager-pbs")
   (count=2:)
   (label="subjob 0")
   (environment=(GLOBUS_DUROC_SUBJOB_INDEX 0)
                (LD_LIBRARY_PATH /usr/local/globus-4.0.3/lib/))
   (directory="/home/grid/Torque/simple")
   (executable="/bin/hostname")
   (stdout=hostnameOutput)
   (stderr=hostnameError)
)
-----------------------
Output of "globusrun -d -f torque.rsl" is:

making globus_duroc request: +(&("dryrun" = "yes" )("resourceManagerContact" =
"Server.eng4.shirazu.ac.ir/jobmanager-pbs" )("count" = "2:" )("label" = "subjob
0" )("environment" = ("GLOBUS_DUROC_SUBJOB_INDEX" "0" ) ("LD_LIBRARY_PATH"
"/usr/local/globus-4.0.3/lib/" ) )("directory" = "/home/grid/Torque/simple"
)("executable" = "/bin/hostname" )("stdout" = "hostnameOutput" )("stderr" =
"hostnameError" ))
duroc request status: 0
duroc job contact: "1"
Dryrun successful.

That I think must give us an error.
------- Comment #1 From 2007-05-07 11:09:53 -------
Thanks for the report.  Yea, looks like a bug.  However, this does not look
like a high priority bug for us at the present time, so lowering priority to 5.
------- Comment #2 From 2012-09-12 13:20:33 -------
We've migrated our issue tracking software to jira.globus.org. This issue is
being traced in
http://jira.globus.org/browse/GT-277