Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 471328

Summary:	Grid: Jobs removed using condor_rm remain in cumin
Product:	Red Hat Enterprise MRG	Reporter:	William Henry <whenry>
Component:	cumin	Assignee:	Justin Ross <jross>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Frantisek Reznicek <freznice>
Severity:	urgent	Docs Contact:
Priority:	medium
Version:	1.1	CC:	esammons, iboverma, jross
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-08-21 17:26:05 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 William Henry 2008-11-12 23:51:07 UTC

Description of problem:

I had several job clusters that I was removing. I decided to be clever and remove them using condor_rm instead of cumin.  However all the jobs remained in cumin despite being removed from condor - verified using condor_q | grep <username>. 

I tried removing the jobs in cumin too but of course they are not in condor anymore to remove. So they remain.


Version-Release number of selected component (if applicable):


How reproducible:

Send in a cluster of jobs.  Wait until the jobs show up in cumin. from the prompt run condor_rm with the cluster ID# (i.e. all the jobs in that cluster). Review in cumin. Try removing in Cumin.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Justin Ross 2009-02-23 20:17:15 UTC

This bug is pretty old.  My testing shows this to be fixed as of revision 3123.