Bug 699731

Summary:	Beaker takes back the reserved machine upon panic
Product:	[Retired] Beaker	Reporter:	Vivek Goyal <vgoyal>
Component:	scheduler	Assignee:	Bill Peck <bpeck>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	0.7	CC:	bpeck, dcallagh, jburke, 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:	2011-04-26 14:02:02 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 Vivek Goyal 2011-04-26 13:46:31 UTC

Description of problem:

I reserved a system and I was setting it up for reproducing one of the panics somebody had reported. Upon panic, I wanted to capture kernel crash dump. Hence I manually crashed the system to make sure kdump works. Few seconds after panic, beaker took the machine away.

This does not sound right. As long as I am with-in my reservation duration, beaker should not take the machine away.

Also the very fact I am trying to reserve the machine is to reproduce the panics and debug these panics. If beaker takes the machine away on first panic, how can one debug panics on beaker systems.


My recipe id is: J:77081

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


How reproducible:


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


Expected results:


Additional info:

Comment 1 Bill Peck 2011-04-26 14:02:02 UTC

If you use the webUI reserve workflow it automatically adds the following to the recipe:

<watchdog panic="ignore"/>


You can clone the job you referenced above and change <watchdog panic="None"/> to <watchdog panic="ignore"/> as well.