1.1 KiB
1.1 KiB
P0: combat_turns Column Migration (bf-1bvca)
Problem
acb-index-builder crashed every 15-min cycle with error: column m.combat_turns does not exist
Solution
Added migration to declarative-config k8s/iad-acb/ai-code-battle/acb-schema-init.yml:
ALTER TABLE matches ADD COLUMN IF NOT EXISTS combat_turns INTEGER NOT NULL DEFAULT 0;
Also bumped rollout annotation from v6-playlists-tables to v7-combat-turns to force schema-init Pod restart.
Commits
- jedarden/declarative-config@845d59d - Initial migration SQL added
- jedarden/declarative-config@b623409 - This bead: Bumped annotation from
v7-combat-turnstov8-combat-turns-2024to force schema-init pod restart
Verification
- ArgoCD will auto-sync the Deployment annotation change
- Schema-init Pod will restart and apply the migration
- acb-index-builder should succeed on next cycle
Note: The migration SQL was already present at line 283 of acb-schema-init.yml. The issue was that the schema-init pod had not been restarted since the migration was added, so the production database still lacked the combat_turns column. The annotation bump forces the restart.