From 680dd1a6637efe7ce099497ec20650c2a2cd0f52 Mon Sep 17 00:00:00 2001 From: Paul Vinciguerra Date: Mon, 28 Jan 2019 12:37:50 -0500 Subject: [PATCH] Identify the gerrit source when logging stream-events errors. Was found to be useful while troubleshooting. Change-Id: I363afc0f8c5044967d30a75b591b634ecd423443 Signed-off-by: Paul Vinciguerra --- zuul/driver/gerrit/gerritconnection.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/zuul/driver/gerrit/gerritconnection.py b/zuul/driver/gerrit/gerritconnection.py index ec949ceaf6..2a0c3a166d 100644 --- a/zuul/driver/gerrit/gerritconnection.py +++ b/zuul/driver/gerrit/gerritconnection.py @@ -269,7 +269,8 @@ class GerritWatcher(threading.Thread): if ret and ret not in [-1, 130]: raise Exception("Gerrit error executing stream-events") except Exception: - self.log.exception("Exception on ssh event stream:") + self.log.exception("Exception on ssh event stream with %s:", + self.gerrit_connection.connection_name) time.sleep(5) finally: # If we don't close on exceptions to connect we can leak the