25 lines
896 B
Markdown
25 lines
896 B
Markdown
|
---
|
||
|
|
okf: "0.1"
|
||
|
|
type: decision
|
||
|
|
visibility: private
|
||
|
|
status: active
|
||
|
|
updated: 2026-08-03
|
||
|
|
links:
|
||
|
|
- ../services/job-deploy-runner.md
|
||
|
|
- ../runbooks/deploy-runner-install.md
|
||
|
|
---
|
||
|
|
|
||
|
|
# deploy-runner — co bylo zepsute (uzasadnienie zmiany toru redeployu)
|
||
|
|
|
||
|
|
## What was broken
|
||
|
|
|
||
|
|
The executor ran `scripts/deploy/deploy-node.sh <node> <service>` **inside its own
|
||
|
|
container**. That script ignores both arguments, and expects a repo at
|
||
|
|
`${HOME}/homelab-codex-ws` — inside the container `HOME=/home/homelab`, so it
|
||
|
|
exited at line 18 with `Error: Repository not found`. Behind that failure sat
|
||
|
|
three more: no `git`, no `docker` CLI in the image, and — had it ever got that
|
||
|
|
far — it would have deployed the **executor host's** entire service set, not the
|
||
|
|
action's target node/service. Every `healthcheck_failed → redeploy` dead-ended
|
||
|
|
(recon `docs/architecture/RECON-multiagent-2026-07-27.md`, D14/D15).
|
||
|
|
|