Bug 1138486 - initial watchdog time configurable per system
Summary: initial watchdog time configurable per system
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Beaker
Classification: Retired
Component: general
Version: 0.17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-05 00:28 UTC by Dan Callaghan
Modified: 2020-11-12 21:42 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-11-12 21:42:51 UTC
Embargoed:


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.