From 7b2e7a71d5f0e133e90f1a14d632922cee97cdfe Mon Sep 17 00:00:00 2001
From: Benjamin Schanzel <benjamin.schanzel@bmw.de>
Date: Tue, 11 May 2021 16:34:46 +0200
Subject: [PATCH] Log Ansible Error Lines Completely

We truncate ansible log lines to 1024 chars. This can be troublesome
when dealing with Ansible errors containing tracebacks, which can
exceed this limit.
To make tracing errors more straight-forward, don't truncate lines that
indicate an Ansible error.

Change-Id: Ide8e0f2d960226cccef725047e509bd98f019d5b
---
 zuul/executor/server.py | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/zuul/executor/server.py b/zuul/executor/server.py
index b49f9a0f70..c6b86a3791 100644
--- a/zuul/executor/server.py
+++ b/zuul/executor/server.py
@@ -2389,7 +2389,10 @@ class AnsibleJob(object):
                     idx += 1
                 if idx < BUFFER_LINES_FOR_SYNTAX:
                     syntax_buffer.append(line)
-                line = line[:1024].rstrip()
+
+                if not line.startswith(b'fatal'):
+                    line = line[:1024].rstrip()
+
                 ansible_log.debug("Ansible output: %s" % (line,))
             self.log.debug("Ansible output terminated")
             try: