Bug 699731 - Beaker takes back the reserved machine upon panic
Summary: Beaker takes back the reserved machine upon panic
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Beaker
Classification: Retired
Component: scheduler
Version: 0.7
Hardware: Unspecified
OS: Unspecified
medium
unspecified vote
Target Milestone: ---
Assignee: Bill Peck
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-26 13:46 UTC by Vivek Goyal
Modified: 2011-04-26 14:02 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-26 14:02:02 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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