feat(fv-ml1): daily drift alarm for the seat inventory

Wires scripts/seat-inventory.py --check to a user systemd timer on nh3-dev
(09:15 daily, Persistent=true so a missed run fires on next boot) that posts to
althing when the committed document stops matching the live box.

Alarms rather than auto-committing. A drift means something changed on the HOST,
which deserves a human look -- silently regenerating the doc would erase the
evidence of when the change happened and why, which is how the char-rp
substitution went unnoticed for three weeks.

The alarm includes the changed table rows, not just the fact of divergence, so
it does not send the reader hunting.

⚠ The post goes --to infra-ops, which is the fleet ops handle the reading
session also runs as. That is the documented exception -- a memo from cron to a
future session, the same pattern as the Beszel alerts -- so the message says so
in its first line, to stop a future session triaging its own alarm as peer mail
and trying to reply to it.

SuccessExitStatus=0 1 because a detected drift is a deliberate non-zero exit,
not a unit failure.

This commit is contained in:

2026-09-13 23:11:46 -07:00

parent a91b841d86

commit c2a70c13db

3 changed files with 74 additions and 0 deletions

									
										scripts/seat-inventory-drift.service
									
		+9
		
												View File
												
				@@ -0,0 +1,9 @@

				[Unit]

				Description=fv-ml1 seat inventory drift check (alarms to althing)

				After=network-online.target

				[Service]

				Type=oneshot

				ExecStart=/home/lkraven/development/eshpfi-management/scripts/seat-inventory-drift-check.sh

				# a drift is a non-zero exit by design; don't let systemd log it as a failure

				SuccessExitStatus=0 1