jedarden/ai-code-battle
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

notes(bf-1bvca): update status - migration complete, blocked by cluster CPU

Browse source 
- Migration SQL already present in schema-init (line 46, line 305)
- Bumped checksum annotation from v9 to v10 and pushed to declarative-config
- Cluster CPU constraint blocking all pods including PostgreSQL
- No CNPG cluster resource found - DB cannot start
- Schema-init cannot apply migrations without DB connection
- Index-builder cannot verify fix without DB

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
jedarden 2026-06-03 23:21:47 -04:00
parent 7aed869277
commit 4f12c67a4e
1 changed files with 27 additions and 23 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

50
notes/bf-1bvca.md
View file

@ -2,12 +2,11 @@
## Summary
The `combat_turns` column migration has been successfully deployed to apexalgo-iad. The migration code is complete, committed, and pushed to declarative-config. Verification is blocked by cluster CPU resource constraints.
The `combat_turns` column migration has been successfully deployed to declarative-config. The migration code is complete, committed, and pushed. Verification is **blocked by cluster CPU resource constraints** - all pods including the PostgreSQL database are stuck in Pending state.
## Changes Made
### 1. Schema Migration Added to declarative-config
## Changes Made (This Session)
### 1. Schema Migration - Already Present
File: `~/declarative-config/k8s/apexalgo-iad/ai-code-battle/acb-schema-init.yml`
- **Line 46** - CREATE TABLE statement:
@ -20,18 +19,15 @@ File: `~/declarative-config/k8s/apexalgo-iad/ai-code-battle/acb-schema-init.yml`
ALTER TABLE matches ADD COLUMN IF NOT EXISTS combat_turns INTEGER NOT NULL DEFAULT 0;
```
### 2. Rollout Annotation Bumped
### 2. Rollout Annotation Bumped (This Session)
Deployment annotation bumped to trigger schema-init pod restart:
```yaml
checksum/schema: "v7-combat-turns-migration-2026-06-03-m"
checksum/schema: "v10-combat-turns-force-apply-2026-06-03-bf-1bvca"
```
Previous: `v9-combat-turns-migration-2026-06-03-bf-1bvca-force-reapply`
### 3. Commits to declarative-config
- `503724e` fix(apexalgo-iad): bump schema-init annotation to v7 for combat_turns migration
- `85719b0` feat(acb-schema-init): bump annotation to reapply schema migrations
- `bd44456` fix(acb-schema-init): bump rollout annotation to v5-combat-turns-migration-2026-06-03-k
### 3. Commit to declarative-config (This Session)
- `6d7439d` fix(acb-schema-init): bump checksum to force reapply combat_turns migration
## Current Cluster Status (BLOCKING)
@ -39,30 +35,36 @@ apexalgo-iad cluster has **Insufficient CPU** - all pods stuck in Pending:
```
NAME READY STATUS RESTARTS AGE
acb-api-5646489f75-l4zmq 0/1 Pending 0 20m
acb-evolver-7654d8b866-psvk5 0/1 Pending 0 20m
acb-index-builder-6669fdbc95-nxwhf 0/1 Pending 0 31m
acb-schema-init-66585d4d6c-5b5j2 1/1 Running 0 7m
acb-worker-bf5bfdb98-g9jnn 0/1 Pending 0 31m
acb-api-5646489f75-l4zmq 0/1 Pending 0 29m
acb-evolver-7654d8b866-psvk5 0/1 Pending 0 29m
acb-index-builder-6669fdbc95-nxwhf 0/1 Pending 0 40m
acb-map-evolver-79ff4cdf6c-7ghg4 0/1 Pending 0 40m
acb-matchmaker-64f6dc5985-vkbbl 0/1 Pending 0 40m
acb-schema-init-6cfbcc9fdc-zqhqj 1/1 Running 0 9m
acb-worker-bf5bfdb98-g9jnn 0/1 Pending 0 40m
```
**Critical:** No PostgreSQL cluster/pod exists - the CNPG cluster resource is not present in the namespace. The schema-init pod is running but cannot connect to PostgreSQL because:
1. The PostgreSQL pod isn't scheduled (CPU constraints)
2. The CNPG Cluster resource may not exist
Error: `0/3 nodes are available: 3 Insufficient cpu`
## Migration Status
| Step | Status |
|------|--------|
| Migration SQL added to schema | ✅ Complete |
| Migration SQL added to schema | ✅ Complete (was already present) |
| Changes committed | ✅ Complete |
| Changes pushed | ✅ Complete |
| Rollout annotation bumped | ✅ Complete |
| Schema-init applies migration | ⏸️ Blocked (cluster CPU) |
| Index-builder verifies fix | ⏸️ Blocked (cluster CPU) |
| Rollout annotation bumped | ✅ Complete (v9 → v10) |
| Schema-init applies migration | ⏸️ Blocked (no PostgreSQL, cluster CPU) |
| Index-builder verifies fix | ⏸️ Blocked (cluster CPU, no DB) |
## Next Steps (Requires Cluster Resources)
Once apexalgo-iad has available CPU:
1. ArgoCD will sync schema-init deployment
Once apexalgo-iad has available CPU and PostgreSQL is running:
1. ArgoCD will sync schema-init deployment (checksum already bumped to v10)
2. Schema-init pod will connect to DB and apply migration
3. Index-builder will schedule and run
4. Verify index-builder logs no longer show "column combat_turns does not exist"
@ -71,3 +73,5 @@ Once apexalgo-iad has available CPU:
- Migration is idempotent (`IF NOT EXISTS`) - safe to reapply
- Index-builder runs on 15-min cycle once scheduled
- The cluster needs CPU capacity to schedule the PostgreSQL pod first
- Without PostgreSQL, schema-init cannot apply migrations and index-builder cannot run