Red Hat Bugzilla – Bug 1309530
recipe start time is a random handful of seconds later than rebooted time
Last modified: 2016-07-07 19:10:18 EDT
Recipes have an overall start and finish time (start_time and finish_time in the database). Beaker also tracks the timestamp at which the system was successfully rebooted in order to kick off the installation at the beginning of the recipe.
Currently the recipe start time is approximately 0-20 seconds later than the rebooted time, because recipe.start_time is populated by beakerd's update_dirty_jobs thread. It runs in a loop every 20 seconds, and when it finds a recipe which is running but has no start time, it sets the start time to now.
This is particularly noticeable in the new recipe UI, which presents the installation progress including relative timestamps. For all our existing recipes, Beaker claims that the reboot happened a few seconds *before* the recipe started which doesn't make much sense.
I think the best option is to record the start time as the earliest of rebooted time, first task start time, or now. (Note that for systems without power control, there is no reboot command so there is no rebooted timestamp, the system simply appears and the first Beaker sees is when the system has checked in after booting Anaconda.)
Patch is merged, but only into results-reporting-improvements-take2 branch for now.
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see email@example.com with any questions
The results-reporting-improvements-take3 branch has been merged to develop.
Beaker 23.0 has been released.