From c16008e67a54ff79a9dc71622c6df18c4ad916a0 Mon Sep 17 00:00:00 2001 From: Ilia Denisov Date: Tue, 14 Jul 2026 11:33:39 +0200 Subject: [PATCH] chore(ansible): pin every host's system timezone to UTC MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The tg (bot) VPS came up on Europe/Moscow while the main host is UTC, so host-level timestamps (journald, file mtimes, cron) sat 3h apart across the fleet. Add a community.general.timezone task to the common role so every provisioned host is UTC (idempotent — a no-op on the already-UTC main host). Applied live to the tg host in the same change; the containerised services run in UTC regardless, so no restart. --- deploy/ansible/roles/common/tasks/main.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/deploy/ansible/roles/common/tasks/main.yml b/deploy/ansible/roles/common/tasks/main.yml index a2da8ba..378b7b9 100644 --- a/deploy/ansible/roles/common/tasks/main.yml +++ b/deploy/ansible/roles/common/tasks/main.yml @@ -150,6 +150,13 @@ enabled: true state: started +# Pin every host to UTC so host-level timestamps (journald, file mtimes, cron) line up +# across the fleet — some VPS images ship a local zone (the tg host came up on MSK). The +# services themselves run in UTC regardless; this is about host-side log correlation. +- name: Set the system timezone to UTC + community.general.timezone: + name: Etc/UTC + # --- Swap file (OOM cushion) --------------------------------------------------- # The prod main host is tight (1.9 GiB) and the per-container memory caps # (docker-compose.prod.yml) sum to more than RAM, so a simultaneous spike could hit