Keep earlier builds recoverable across region image upgrades
Complete the maintainer's server image bump to edb39f by also setting the region build identity, and add REGION_RETAINED so the host keeps the builds that wrote its history on its recovery allowlist; without it the upgraded host would quarantine its own head as unsupported. Record the M8.4 drill (rollout 3.0 s, forced deletion 19.3 s to Ready, epochs 3 to 5) and the maintainer's M8.5 sync. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -2844,3 +2844,19 @@ admission policy and the stage and World0 AppProjects, then ran
|
||||
- Not executed: anything in the cluster (monitoring sync, target health, the
|
||||
`EvoRegionDown` injection), alert delivery (no receiver), and the node log
|
||||
rotation check.
|
||||
|
||||
## M8.4 and M8.5 in-cluster results - 2026-09-30
|
||||
|
||||
- `tools/ops/region-drill.sh dev`, run by the maintainer (idle region, world 100):
|
||||
- start: epoch 3, committed tick 0;
|
||||
- rollout restart: the replacement was Ready in **3010 ms**, at epoch 4 with
|
||||
committed tick 0 (Recreate drain released the lease);
|
||||
- forced deletion: the replacement was Ready in **19268 ms**, at epoch 5 with
|
||||
committed tick 0 (waiting out the 20 s lease);
|
||||
- PASS.
|
||||
- M8.5: the maintainer reports the new server digest pinned and the monitoring
|
||||
project, platform, monitoring app and dev/stage applications synced. Target
|
||||
health and the `EvoRegionDown` injection results were not recorded here.
|
||||
- Image upgrade to `edb39f…`: completed with `REGION_RETAINED=4af72099…`, so the
|
||||
existing dev and stage heads, written by the earlier build, stay recoverable
|
||||
after the upgrade.
|
||||
|
||||
Reference in New Issue
Block a user