Open grid sceduler jobs with no job id in BASE
|Reported by:||Nicklas Nordborg||Owned by:||Nicklas Nordborg|
For some reason a (cufflinks) job was submitted to the cluster but no job id was returned. The job was queued and executed successfully but we could not get any information about it without the job id. Trying to abort the job on the BASE side didn't work either since this triggered a command to the cluster to abort a job with an unknown id (the cluster probably answered with an error message).
The status checking and abort functionality for jobs should be updated to not send commands to the cluster if the job id is not known.
It would also be good if this could be checked before registering the job but I need to check if it is possible to get information about the error in this case.