kevinveenbirkenbachandClaude Opus 5.5 9ce68b0334 fix(web-app-zammad): wait for the current init task to complete in swarm ...

In swarm the role gated init only through "wait for Zammad init (seeds
+ pk-sequence reset)", which checks database state. On an existing
installation that state is already there, so a swarm deploy that
restarts init while Elasticsearch refuses shards passed: the init task
kept failing on the allocation precheck and nothing reported it.

A swarm-only task now runs sys-svc-compose's job_state.sh against the
init service after the seeds wait. It passes once the newest init task
is Complete. If the newest task stays Failed, it fails the deploy
after 60 retries 5 s apart. An init the stack deploy did not restart
is already Complete and passes at once. Compose needs no extra wait,
because railsserver depends on init with
service_completed_successfully.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

2026-10-18 12:33:54 +02:00

..

00_core.yml

refactor(mcp)!: prove the endpoint contract with a CLI test, not a deploy probe

2026-09-01 20:46:26 +02:00

01_manager_ops.yml

fix(web-app-zammad): wait for the current init task to complete in swarm

2026-10-18 12:33:54 +02:00

main.yml

refactor(tasks): enforce and apply a single task-file numbering scheme

2026-07-23 20:01:31 +02:00