Skip to content

2026-07-05 — Sepia Ansible Remediation

Goal

Bring sepia’s Ansible playbooks back in line with the live trixie-era host state after the audit note identified drift.

What I checked

  • /ansible/sepia/setup_fstab.yml
  • /ansible/sepia/setup_ser2net.yml
  • /ansible/sepia/setup_base.yml
  • /ansible/sepia/install_software.yml
  • Live host state via SSH:
  • /etc/fstab
  • /etc/default/locale
  • /etc/ser2net.yaml
  • root cron
  • /root/scripts/btrfs-snap

Notes

  • The live host already had the root cronjobs and btrfs-snap script in place when I rechecked it, so I treated those audit findings as stale and did not change them.
  • The live host fstab uses sepia--vg-trixie--lv for /, UUID=a648c12e-ae5e-4cdc-8cec-48fcc00a7892 for /boot, and UUID=CF86-8F36 for /boot/efi.
  • The live ser2net device ID is usb-FTDI_FT232R_USB_UART_ABAWD44U-if00-port0.
  • setup_base.yml already sets LC_ALL=en_US.UTF-8; install_software.yml already includes man.

Next steps

  • Apply the playbooks on sepia after the playbook files are updated.