Bug 749743 - system not released after job has finished
Summary: system not released after job has finished
Keywords:
Status: CLOSED DUPLICATE of bug 715226
Alias: None
Product: Beaker
Classification: Retired
Component: scheduler
Version: 0.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bill Peck
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-28 08:07 UTC by Jan Stancek
Modified: 2014-08-12 04:33 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-31 22:15:20 UTC
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.