Agent container exits during an isolated repo-free workflow acceptance run #1252

Closed
opened 2026-10-27 13:39:38 +00:00 by sam · 0 comments
Owner

A local workflow admitted through New task reached container dispatch, but the agent container reported a broker authentication error and exited before finishing. The task remained parked with an unknown attempt and no stages. Check compatibility of the locally installed agent image and broker task-grant authentication, then verify a repository-free finish-only workflow end to end.

Acceptance criteria

A finish-only workflow admitted through the dashboard completes through the agent container with its attempt and stage outcome recorded.

Notes

2026-10-27 code review, no fix. Repo-free path is not the cause: container auth (agenttransport/nats/transport.go:87-92) logs in as task- with the run credential, checked by archied taskBroker.TaskSubjects (app/archied/task_broker.go:25) -> ResolveTaskGrant (staterpc/task_grants.go:248). That fails only if the grant is unknown/expired/revoked, the execution identity cannot act, or the image's agent predates the task-user NATS login (sends no user/token). A workflow with no identity is parked earlier with a clear blocker (daemon/workflow_identity.go:37), so it never reaches a container. No code-level defect found; needs the actual attempt logs and the installed agent image build to tell grant failure from image skew. Next step: rebuild/redeploy the agent image and rerun the finish-only acceptance; capture daemon log for 'run credential' lines.

Close reason

No cause in code; likely a stale agent image. Reopen if it reproduces after an agent image redeploy.


Imported from beads archie-core-bv7io · GitHub #1665 · type bug · priority P2 · created 2026-10-13 · closed 2026-10-27

A local workflow admitted through New task reached container dispatch, but the agent container reported a broker authentication error and exited before finishing. The task remained parked with an unknown attempt and no stages. Check compatibility of the locally installed agent image and broker task-grant authentication, then verify a repository-free finish-only workflow end to end. ### Acceptance criteria A finish-only workflow admitted through the dashboard completes through the agent container with its attempt and stage outcome recorded. ### Notes 2026-10-27 code review, no fix. Repo-free path is not the cause: container auth (agenttransport/nats/transport.go:87-92) logs in as task-<id> with the run credential, checked by archied taskBroker.TaskSubjects (app/archied/task_broker.go:25) -> ResolveTaskGrant (staterpc/task_grants.go:248). That fails only if the grant is unknown/expired/revoked, the execution identity cannot act, or the image's agent predates the task-user NATS login (sends no user/token). A workflow with no identity is parked earlier with a clear blocker (daemon/workflow_identity.go:37), so it never reaches a container. No code-level defect found; needs the actual attempt logs and the installed agent image build to tell grant failure from image skew. Next step: rebuild/redeploy the agent image and rerun the finish-only acceptance; capture daemon log for 'run credential' lines. ### Close reason No cause in code; likely a stale agent image. Reopen if it reproduces after an agent image redeploy. --- _Imported from beads `archie-core-bv7io` · GitHub #1665 · type bug · priority P2 · created 2026-10-13 · closed 2026-10-27_
sam added the mediumbug labels 2026-10-27 13:39:38 +00:00
sam self-assigned this 2026-10-27 13:39:38 +00:00
sam closed this issue 2026-10-27 13:39:38 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1252