chore(ci): dump Docker/systemd state from the staging node when a deploy fails #69

Merged
jfraeys merged 1 commit from jfraeys/chore/staging-failure-diagnostics into main 2026-10-11 16:10:09 -04:00
Owner

Run 475: crowdsec : Re-verify the firewall bouncer failed after all 12 retries with No such container: crowdsec-crowdsec-1, right after flush_handlers ran hardening : Restart Docker. Reading the roles doesn't explain why the container vanished (daemon.json has live-restore: true), and the node is destroyed after every failure. On a failed deploy the staging check now prints docker ps -a, selected docker info lines, docker/containerd unit state and the last 30 docker journal lines for the failing node (no secrets: names, statuses, daemon log). Tested the snippet locally via ansible ad-hoc. 🤖 Generated with Claude Code

Run 475: `crowdsec : Re-verify the firewall bouncer` failed after all 12 retries with `No such container: crowdsec-crowdsec-1`, right after `flush_handlers` ran `hardening : Restart Docker`. Reading the roles doesn't explain why the container vanished (daemon.json has live-restore: true), and the node is destroyed after every failure. On a failed deploy the staging check now prints `docker ps -a`, selected `docker info` lines, docker/containerd unit state and the last 30 docker journal lines for the failing node (no secrets: names, statuses, daemon log). Tested the snippet locally via ansible ad-hoc. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
chore(ci): dump Docker/systemd state from the staging node when a deploy fails
All checks were successful
Lint / lint (pull_request) Successful in 1m45s
Secret scan / scan (pull_request) Successful in 14s
6bfb4c8629
Run 475 lost the crowdsec container after a Docker restart handler and the node was destroyed before anything
could be inspected. Print docker ps -a, docker info highlights, unit state and the docker journal on failure.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
jfraeys/infra!69
No description provided.