Bug 451794

Summary:	gridmanager keeps running after rm -forcex
Product:	Red Hat Enterprise MRG	Reporter:	Matthew Farrellee <matt>
Component:	grid	Assignee:	Matthew Farrellee <matt>
Status:	CLOSED WONTFIX	QA Contact:	Kim van der Riet <kim.vdriet>
Severity:	low	Docs Contact:
Priority:	low
Version:	1.0	CC:	jfrey
Target Milestone:	1.1
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-11-04 14:44:22 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Matthew Farrellee 2008-06-17 13:37:46 UTC

The gridmanager continues to run when there are no jobs to service, at least
when jobs are removed with rm -forcex.

The gridmanager should notice there are no more jobs and terminate.

Comment 1 Jaime Frey 2008-09-10 20:24:51 UTC

The current behavior is intentional and happens for all grid universe jobs. We saw it as advantageous that the gridmanager continued to trying removing jobs from the remote resource after the user did a condor_rm -forcex. Some on the team disagree and think the gridmanager should give up on jobs once a -forcex is performed.