Bug 749743

Summary:	system not released after job has finished
Product:	[Retired] Beaker	Reporter:	Jan Stancek <jstancek>
Component:	scheduler	Assignee:	Bill Peck <bpeck>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.7	CC:	bpeck, dcallagh, gozen, jburke, mcsontos, pbunyan, rmancy, stl
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-10-31 22:15:20 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 Jan Stancek 2011-10-28 08:07:01 UTC

Description of problem:
Rarely I see machines still being reserved by some user, even though their jobs are finished/cancelled.

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

How reproducible:
rarely

Steps to Reproduce:
- unknown, it looks like that job has been canceled before system was powered on
  
Actual results:
job finished (was canceled) but machine is still reserved by user

Expected results:
when job is finished system should be returned

Additional info:

Comment 2 Dan Callaghan 2011-10-31 22:15:20 UTC

As mentioned on bug 715226, the workaround is to use the bkr job-cancel command to cancel the (already-cancelled) recipeset.

*** This bug has been marked as a duplicate of bug 715226 ***