Bug 1138486

Summary: initial watchdog time configurable per system
Product: [Retired] Beaker Reporter: Dan Callaghan <dcallagh>
Component: generalAssignee: beaker-dev-list
Status: CLOSED WONTFIX QA Contact: tools-bugs <tools-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 0.17CC: cbouchar
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-12 21:42:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dan Callaghan 2014-09-05 00:28:24 UTC 
The initial watchdog time (from when the system is rebooted at the start of a recipe, until it reached Anaconda %pre which triggers install_start which extends the watchdog) is currently set to the time of the first task (often /distribution/install which has TaskTime: 20 minutes) plus 30 minutes leeway = 50 minutes.

For most normal systems, which POST in a few minutes or less, 50 minutes is far too long. If the installer fails to start for some reason, that means Beaker will wait 50 minutes before the watchdog aborts the recipe.

For some unusual hardware, which takes a very long time to POST, 50 minutes may not be enough time to start Anaconda.

The initial watchdog should not be based on the first task in the recipe, but rather should be configurable per system with a sane default (perhaps 15 minutes), similar to the configurable power quiescent period we added not long ago.
Comment 1 Dan Callaghan 2014-09-05 00:28:52 UTC 
I have an old patch here which just hardcoded 15 minutes:

http://gerrit.beaker-project.org/2902