mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-08 11:46:35 +00:00
kevinveenbirkenbachandClaude Opus 5
3748e3ee00
Two places in the DR drill ruled on a systemd unit without looking at what the unit was doing. [8b/9] took the exit code of `systemctl try-restart nfs-ganesha` as the verdict. The unit carries Restart=on-failure from the role's own drop-in, and that drop-in also hangs a 20 second readiness probe on port 2049 as ExecStartPost. Right after the backing FS is wiped and restored, that probe runs out while the container still waits on its own stale NFS mount, so systemd kills the daemon it just started and reports a failed start - then restarts it three seconds later and succeeds. Measured in run 34699757369, jobs 103572236910 (Matrix#0) and 103638497583 (Gitea#0): 'Control process exited, code=exited, status=124', 'Failed to start', then 'Scheduled restart job, restart counter is at 1'. The restart attempt may now fail; the assertion is a bounded wait on is-active, and it aborts loudly with systemctl status when the unit never arrives. The coherence probe that follows is unchanged and still has to pass. [0/9] waited for in-flight backups with `systemctl is-active --quiet 'svc-bkp-*.service'` and did not wait. In job 103588089327 (Moodle#0) the volume unit ran from 01:00:56 to 01:01:12 while that loop returned after 0.36s for four nodes. The drill then attached to the running job instead of starting its own, and [3b/9] refused the generation it found because it predated the drill by ten seconds. That second change is a hardening, not a proven fix: the reason the loop returned early is still unknown. The obvious explanation does not hold - the systemd manual says is-active "Returns an exit code 0 if at least one is active", so a pattern matching one running unit among four idle ones should have blocked. list-units --state=active expresses the same intent without relying on that semantics. Closing the gap needs the call run on a node with exactly that mix, which no local container offers. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Test Utilities 🧪
This directory holds the operational side of testing in Infinito.Nexus.
These assets are meant to support confidence, not ceremony. They help the project validate real-world behavior across local development, CI environments, and deployment-oriented smoke tests. The emphasis is on practical feedback: when something breaks, the surrounding test tooling should make the failure easier to understand, easier to reproduce, and easier to clean up. 🚀
Good changes in this area usually make the test experience more:
- repeatable
- diagnosable
- environment-aware
- safe to rerun
The ideal outcome is boring reliability: contributors should be able to trust that a test run says something meaningful about the system, not just about the machine that happened to execute it. ✅