pal-e-docs

Bug: NodeClockNotSynchronising — NTP not configured

bug-node-clock-ntp Todo

bug resolved
Project

Bug: NodeClockNotSynchronising

Problem

Alertmanager fires NodeClockNotSynchronising warning. Prometheus node_exporter detects the host clock is not synced to an NTP source.

Root Cause

The host (Arch Linux) has no NTP service enabled. systemd-timesyncd is available by default on Arch but may not be enabled. No Salt state manages time synchronization.

Fix

Add a Salt state to enable systemd-timesyncd (or install chrony for better accuracy). Verify with timedatectl status showing "System clock synchronized: yes".

Impact

Clock drift can cause TLS certificate validation failures, log timestamp skew, and Kubernetes lease expiration issues. Currently minor but could cause cascading failures if drift grows.

Acceptance Criteria

  • timedatectl status shows clock synchronized
  • NodeClockNotSynchronising alert resolves in Alertmanager
  • Salt state exists and is idempotent
  • audit-observability-baseline-2026-03-13 — discovered during baseline audit
  • phase-observability-3-alerting — parent phase