zuul/playbooks/zuul-stream
Tobias Henkel 30cb2b1484
Fix unreachable nodes detection
According to the docs ansible is expected to return 3 if there were
unreachable nodes. Zuul reacts on this and retries the job. However
ansible really returns 4 in this case [1] which actually is the code
for a parse error (which doesn't make sense to retry).

To work around that add a simple callback plugin that gets notified if
there are unreachable nodes and write the information about which
nodes failed to a special file beneath the job-output.txt. The
executor can detect this and react properly then. Further we have the
information about which nodes failed in this file which gets uploaded
to the log server too if it exists.

[1] https://github.com/ansible/ansible/issues/19720

Change-Id: I6d609835dba18b50dcbe883d01c6229ce4e38d91
2018-09-29 13:13:00 +02:00
..
fixtures Do late decoding of log stream buffer 2017-10-27 07:59:32 +02:00
templates Rename action-general to actiongeneral 2018-06-15 07:08:24 +02:00
functional.yaml Fix unreachable nodes detection 2018-09-29 13:13:00 +02:00
post-ara.yaml Move ara output generation to post playbook 2017-09-03 18:11:41 -05:00
post.yaml Move ara output generation to post playbook 2017-09-03 18:11:41 -05:00
pre.yaml Remove bindep_command lines 2017-09-02 08:26:59 -05:00