fix: serialize Tower migration validation
This commit is contained in:
@@ -7794,3 +7794,8 @@ Validation before live deployment:
|
||||
|
||||
Next:
|
||||
- Run the complete readiness gate, deploy to Tower/PostGIS, provision the official snapshots and verify current/evolution selection end to end in the internal browser.
|
||||
|
||||
Live deployment correction:
|
||||
- The first Tower rollout exposed a deployment race: all-in-one startup and `live_migration_smoke.sh` both began `alembic upgrade head` after PostgreSQL became reachable.
|
||||
- Startup committed head `202607140001`; the concurrent smoke transaction rolled back on a duplicate first column. Database contents and the successful migration remained healthy.
|
||||
- Both Tower deploy entry points now wait for the `geointel` container healthcheck, which includes completed startup migrations and backend readiness, before launching the independent migration smoke.
|
||||
|
||||
Reference in New Issue
Block a user