Bug 593454

Summary:	Systems are not released back to the pool when a job is canceled
Product:	[Retired] Beaker	Reporter:	Mike Gahagan <mgahagan>
Component:	lab controller	Assignee:	Bill Peck <bpeck>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	0.5	CC:	bpeck, kbaker, mcsontos, rmancy
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:	2010-06-16 19:26:56 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 Mike Gahagan 2010-05-18 19:57:35 UTC

Description of problem:
When canceling a job last week, I noticed approximately 5 systems were not released back to the pool. When I tried to release the system manually it failed informing me it was part of a running job

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

How reproducible:
only has happened once

Steps to Reproduce:
1.
2.
3.
  
Actual results:
Systems unusable by others when job is cancelled

Expected results:
Systems are released

Additional info:
https://beaker.engineering.redhat.com/jobs/405

Comment 1 Bill Peck 2010-06-16 19:26:56 UTC

this shouldn't be a problem anymore.  If you see this again please re-open this bug.

Thanks!