Bug 6768 – Held Condor jobs should be reported as SUSPENDED by GRAM

Bug 6768 - Held Condor jobs should be reported as SUSPENDED by GRAM

Summary:

Held Condor jobs should be reported as SUSPENDED by GRAM

Status:	RESOLVED LATER

Product:	GRAM
Component:	gt2 Gatekeeper/Jobmanager
Version:	4.2.1
Platform:	All All

Importance:	P3 normal
Target Milestone:	---
Assigned To:	Stuart Martin

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-06-16 14:21 by Jaime Frey
Modified:	2012-09-12 13:37 (History)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

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

Description From Jaime Frey 2009-06-16 14:21:16

I just spent an hour with Igor Sfiligoi trying to figure out why several
hundred of his Condor glideins that GRAM claimed were ACTIVE weren't reporting
to his collector. It turned out they were held in the Condor system behind a
GRAM gatekeeper.

We believe when a Condor job is in the held state, GRAM should report the job's
status as SUSPENDED, since it certainly isn't running. This should be a fairly
simple change to make in the condor.pm script. I can write up a patch.

------- Comment #1 From Joe Bester 2012-09-12 13:37:42 -------

We've migrated our issue tracking software to jira.globus.org. This issue is
being tracked at http://jira.globus.org/browse/GT-48