Description of problem:
beaker-watchdog is aborting recipes too early.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Have not confirmed this yet, but from looking at this commit:
it seems like Beaker will return a watchdog as 'expired' if *any* recipe in the set has kill time in the past. It should be only if *all* recipes in the set have kill time in the past. However, this doesn't yet fully explain the behaviour we are seeing.
I noticed that the guest recipes are always aborted exactly 4 hours after the host recipe finished /distribution/virt/start, I feel like that must be a clue as to what exactly is going wrong...
Okay so the mystery of the 4 hours is solved: beah extends the watchdog by 4 hours when a task finishes (I don't know what for).
The issue here is really just with the Watchdog.by_status query.
On Gerrit: http://gerrit.beaker-project.org/3218
Steps to reproduce:
1. Submit a job with a host recipe containing a guest recipe, with the following tasks:
Job runs up until reservesys in the guest, but instead of staying reserved for 24 hours the job is terminated by external watchdog 4 hours after /distribution/virt/start completed.
Job runs successfully. reservesys task in the guest reserves for 24 hours.
beaker-0.17.2 has been released.