tree c7bc556d3ae6735b43da2fe8bd555661ef668211
parent cef224d1628a73ef70a5d7f06fce16c312859ba5
author James E. Blair <jeblair@redhat.com> 1481739135 -0800
committer James E. Blair <jeblair@redhat.com> 1481739135 -0800

Fix watchdog timeout fix

In I6cae11c1e89f6ccc78cb5bfaf61ef78e846e87be, we attempted to fix
an error where long-running workers never reset their watchdog
timeout flag, meaning that once a job timed out, all further jobs
on that worker timed out.  That change cleared the flag each time
ansible ran.  However, that flag is also used in conjunction with
the abort flag to determine whether a failed or null result should
be sent back to Zuul (a null result will cause a job to be
rescheduled).  By clearing the flag before, say, a post playbook
we would lose the information that the abort was due to a timeout
rather than a direct abort request, and return the null result to
Zuul.  This means all jobs that timeout would be relaunched.

Instead of clearing the flag before each ansible run, clear it once
at the start of the job launch.  This means it will be set for any
ansible timeout.  That should be fine for both the aborted job check
as well as the new "timed out" log message.

The typo this change corrects indicates this was the intended logic.

Change-Id: Ie31409a7706b6cf4d7ce858b4d5f0c00e4ee31da