ai-code-battle/notes/bf-1bvca.md

BF-1BVCA: combat_turns Column Migration

Status: Migration deployed, blocked by cluster issues

Work Completed

1. Schema Migration Added - declarative-config/k8s/apexalgo-iad/ai-code-battle/acb-schema-init.yml:

   • Line 46: combat_turns INTEGER NOT NULL DEFAULT 0 in CREATE TABLE
   • Line 305: ALTER TABLE matches ADD COLUMN IF NOT EXISTS combat_turns INTEGER NOT NULL DEFAULT 0;

2. Rollout Annotation Bumped:

   • Updated to v14-combat-turns-2026-06-03-bf-1bvca-force-restart

3. Changes Committed and Pushed:

   • Commit: 1ec0c25 - "feat(apexalgo-iad): bump schema-init annotation to v14 - force restart for combat_turns migration"

Current Blockers (Infrastructure, not migration-related)

1. Database Cluster Down: cnpg-apexalgo in cnpg namespace shows:

   STATUS: Waiting for the instances to become active
   INSTANCES: 0/3 ready
   

   The schema-init pod cannot apply migrations without a database connection.

2. CPU Constraints: Index-builder pod pending:

   Warning FailedScheduling: 0/3 nodes are available: 3 Insufficient cpu.
   

Verification Plan

Once cluster is healthy:

1. Verify cnpg-apexalgo cluster reaches Healthy status with 3/3 instances
2. Schema-init pod should connect and apply migrations (check logs for "Schema applied")
3. Index-builder pod should schedule successfully (check kubectl get pods)
4. Verify index-builder logs show no "column combat_turns does not exist" errors

Migration Content

-- In CREATE TABLE matches statement
combat_turns  INTEGER NOT NULL DEFAULT 0,

-- In migrations section
ALTER TABLE matches ADD COLUMN IF NOT EXISTS combat_turns INTEGER NOT NULL DEFAULT 0;

This migration is idempotent (uses IF NOT EXISTS) and will apply cleanly when the database becomes available.