Project

General

Profile

Bug #24057

jobsub_q --better-analyze often asks wrong schedd for job info

Added by Dennis Box about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
02/17/2020
Due date:
% Done:

0%

Estimated time:
First Occurred:
Occurs In:
Stakeholders:
Duration:

Description

See INC000001092616.

The jobsub_q command, for example:
jobsub_q -G mu2e --better-analyze --jobid

Is trying to ask schedd jobsub03.fnal.gov to analyze why job 2898203.0 has not started.

There is intermediate code between the above jobsub_q command and the resulting condor_q command that finds the least busy schedd (there are currently 3) and directs the query to that one. In the above example I found this in the log:

condor_q -allusers -nobatch -name jobsub02.fnal.gov -better-analyze -constraint 'True && True && regexp("jobsub03.fnal.gov#2898203\.0#.*",GlobalJobId) && True'.

-name jobsub02.fnal.gov should be -name jobsub03.fnal.gov. This got through CI as we only have one schedd on our test setup.



Also available in: Atom PDF