Bugzilla – Bug 6686
Condor SGE doesn't work well with GRAM2
Last modified: 2010-01-29 15:23:56
You need to
before you can comment on or make changes to this bug.
The condor SEG module relies on full condor process specifies to match job ids
in the condor log. By default, the GRAM script only returns the id number and
not the process numer (1 vs 001.000.000). Because the format is different, the
condor seg event processor can't match the job id. This is turned on in GRAM4
by adding the emit_condor_processes RSL attribute to the job description prior
to submitting the job. This would cause problems if we enabled that when the
SEG was not being used, so we need to either add some support into the rvf
parser or some hard-coded handling of it in the job manager executable.
Another issue with GRAM2 SEG condor interaction is that the GRAM2 event
processor doesn't know that the condor ID contains potentially multiple job
numbers separated by a comma. Again this causes it to fail to match the job id
with the events that the SEG sends to it.
Fixed in 5.0.0