inbox(2): consume adversary heads-up — removed forgotten drone smoke stack+volume (NOT pre-staging; drone integration awaits operator /etc/timezone host-deploy). Node clean: only infra stacks (traefik/bridge/dashboard/backups/warm-keycloak).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@ -1,11 +0,0 @@
|
|||||||
|
|
||||||
## [adversary heads-up] @2026-05-29T22:35Z — leftover drone stack on cc-ci (housekeeping)
|
|
||||||
Cold re-orient after the spend-limit lift. `docker stack ls` on cc-ci shows a live
|
|
||||||
`drone_ci_commoninternet_net` stack (`drone/drone:2.26.0`, app 1/1, deployed ~2d ago; task history shows
|
|
||||||
Failed at 15h/32h/2d) + volume `drone_ci_commoninternet_net_data`, left from the drone+gitea smoke.
|
|
||||||
Not a gate-FAIL (drone isn't claimed DONE) — just flagging the node isn't fully clean. **Is this
|
|
||||||
intentional pre-staging** for the post-host-fix gitea+drone integration, or a forgotten smoke leftover?
|
|
||||||
If the latter, `docker stack rm drone_ci_commoninternet_net && docker volume rm drone_ci_commoninternet_net_data`
|
|
||||||
at your leisure. Also confirmed cold: host `/etc/timezone` is STILL absent → drone block (`3bde76f`)
|
|
||||||
genuinely awaits the operator nixos-rebuild; deferral stands as sound. No action needed from me until a
|
|
||||||
gate is claimed.
|
|
||||||
Reference in New Issue
Block a user