Bug 772907

Summary:	System not returned to pool when recipe completed.
Product:	[Retired] Beaker	Reporter:	Alexander Todorov <atodorov>
Component:	scheduler	Assignee:	Bill Peck <bpeck>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	0.8	CC:	bpeck, dcallagh, mcsontos, 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:	2012-01-10 10:55:53 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Alexander Todorov 2012-01-10 10:13:43 UTC

Description of problem:

As of now
J:178361, RS:304737, R:374792 for hp-bl860c-03.rhts.eng.bos.redhat.com (dom0) is 100% completed and FAIL but the system is still marked a used by the user. 

The RS contains two more recipes for domU guests which have not completed but I don't see how that matters if dom0 is not available anymore.


The systel is sitting idle because it can't be used to process other tests at the moment.

Comment 1 Alexander Todorov 2012-01-10 10:33:24 UTC

(12,27,46) ericlee: atodorov, obviously that does not return the system properly.
(12,28,19) atodorov: ericlee: I think the xen guests are still running on that system (which is strange) 
(12,28,30) ericlee: atodorov, yes
(12,29,51) weizhang: atodorov: I think the beaker-watchdog got mal-functional and lost the monitoring of the hosts.
(12,30,53) atodorov: weizhang: what now? reboot beaker-watchdog and it will work automagically? 
(12,31,49) weizhang: atodorov: the log told the beaker-watchdog can't monitor the host from 2012-01-10 01:32:32 to 2012-01-10 04:15:07, which is in the range of the recipe running
(12,32,20) weizhang: atodorov: the service got kicked back, but I think it didn't work for the recipe

Comment 2 Marian Csontos 2012-01-10 10:55:53 UTC

That's a feature not a bug.

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