Bug 1348018 - no watchdog for recipe after reboot
Summary: no watchdog for recipe after reboot
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: scheduler
Version: develop
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 23.0
Assignee: Roman Joost
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-20 01:18 UTC by Dan Callaghan
Modified: 2016-07-07 23:09 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-07-07 23:09:49 UTC
Embargoed:


Attachments (Terms of Use)

Description Dan Callaghan 2016-06-20 01:18:23 UTC
Prior to Beaker 23, when a recipe's system was rebooted it would start the first task in the recipe. That had the very important side effect of setting the watchdog time (to 50 minutes usually, which was the task time for /distribution/install + 30 minutes, see also bug 
1138486).

As part of introducing the new Installing status (bug 991245), we no longer start the first task to indicate the installation has started:

https://git.beaker-project.org/cgit/beaker/commit/?id=0f055ba9961ab218656af20e01725f12043a7e9a

The watchdog time *is* now set when the install_started call happens, which covers most cases, but we do also need the watchdog time to be set immediately after rebooting in case the system never actually powers on (or fails to netboot properly, etc).

For now we could hardcode 50 minutes as the initial watchdog time, to restore the previous behaviour, with bug 1138486 as the RFE for making that configurable.

Comment 1 Dan Callaghan 2016-06-20 01:18:50 UTC
Unreleased regression on develop.

Comment 2 Roman Joost 2016-06-23 06:45:40 UTC
New patch in gerrit:

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

Comment 5 Dan Callaghan 2016-07-07 23:09:49 UTC
Beaker 23.0 has been released.


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