Bugzilla – Bug 6703
PBS scheduler adapter assumes that Globus is installed in the same location on the headnode of a cluster and on the work nodes.
Last modified: 2012-09-12 08:38:48
You need to
before you can comment on or make changes to this bug.
It seems like the PBS scheduler adapter assumes that the Globus toolkit is
installed in the same location on the headnode of a cluster and on its work
nodes (usually this is the case when a shared filesystem is used).
The PBS script generated by the scheduler adapter contains a line such as:
The value for the GLOBUS_LOCATION above is set to the value of GLOBUS_LOCATION
on the headnode. If Globus is installed in a different location on the
headnode than on the work nodes, then this will cause an invalid
GLOBUS_LOCATION value when the job runs on one of the work nodes.
I'm cleaning out old bugs. This was addressed with the -target-globus-location
config option in 5.0