1.6 KiB
1.6 KiB
R5 reload and activation repair
Base SHA: ca28be6ae6.
Result SHA: accompanying commit (resolved via git log -- agents/codex/done/2026-10-19-r5-reload-fix.md).
Changed files: deploy/randomayzer.haproxy.cfg; docs/STAGE1_DEPLOYMENT_RUNBOOK.md; this report and associated inbox/review artifacts.
- Conditional executable HAProxy USR2 reload requires PID1 haproxy with -W/-Ws, complete validated config and worker handoff; unchanged container ID/start/restart count checked. Unknown topology stops.
- HTTP-01-only preparation precedes Caddy Basic Auth activation; TLS SNI route follows it.
- Whole-tree backups require nonempty copies and diff equality; rollback preserves unrelated edits.
Actual verification:
- bash agents/codex/notes/validate-r5-templates.sh: exit 0, Caddy 2.8.4 and HAProxy 3.0.30 configuration valid in isolated fake fixtures.
- bash -n on all 25 runbook bash blocks: exit 0.
- Exact runbook reload function, official HAProxy 3.0 fixture: exit 0, new worker observed and container identity/start/restart count unchanged.
- Same function against non-master PID1 sleep: rejected without changing container identity/start/restart count or running state.
- Temporary fixtures removed after checks; no VPS mutation.
UNVERIFIED: actual VPS process model, config mounts/admin API, active backend names, DNS/TLS, WireGuard peer, existing-site baselines and live acceptance. These remain operator gates, not completed deployment. Blockers: independent rereview pending at report creation. Non-blocking debt: Caddy formatting and explicit forwarded-header warnings in local validation.