From 895dfbe7a446b1aae06aa28bf6192fad1dc9c2ca Mon Sep 17 00:00:00 2001
From: Clark Boylan <clark.boylan@gmail.com>
Date: Sun, 4 Sep 2022 08:32:46 -0700
Subject: [PATCH] Append zuul reboot logs instead of truncating them
Normally this isn't an issue because we run logrotate more frequently
than our weekly cron to upgrade and reboot zuul. But if you need to
manually run the playbook and are referring to the crontab entry to
determine how to run the playbook then the resulting command could
truncate a recent run. Simply append to the file in all cases to avoid
this.
Change-Id: I393741317cccaf447912b1f1517e846c32ee7677
---
playbooks/service-bridge.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/playbooks/service-bridge.yaml b/playbooks/service-bridge.yaml
index d305434260..f4376a82ad 100644
--- a/playbooks/service-bridge.yaml
+++ b/playbooks/service-bridge.yaml
@@ -51,7 +51,7 @@
minute: 1
hour: 0
weekday: 6
- job: "flock -n /var/run/zuul_reboot.lock /usr/local/bin/ansible-playbook -f 20 /home/zuul/src/opendev.org/opendev/system-config/playbooks/zuul_reboot.yaml > /var/log/ansible/zuul_reboot.log 2>&1"
+ job: "flock -n /var/run/zuul_reboot.lock /usr/local/bin/ansible-playbook -f 20 /home/zuul/src/opendev.org/opendev/system-config/playbooks/zuul_reboot.yaml >> /var/log/ansible/zuul_reboot.log 2>&1"
- name: Rotate Zuul restart logs
include_role: