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:
dingo
2026-09-30 10:34:03 -04:00
co-authored by Claude Opus 5.5
parent bcf2eacb5e
commit 4ef0fe8167
8 changed files with 51 additions and 7 deletions
+11
View File
@@ -90,3 +90,14 @@ that is no lower than before.
- **A StatefulSet.** It adds no guarantee the lease does not already provide.
- **A director.** With static single-region assignment, it would be a placeholder
with no authority.
## Amendment: retained builds across image upgrades (2026-09-30)
Each commit records the build that wrote it, and recovery accepts only builds on
the host's allowlist. After an image upgrade, a region's existing head was
therefore written by the previous build. Without `--retained <old build>` the new
host would refuse its own history as unsupported and quarantine. `region/<env>`
now lists earlier builds in `REGION_RETAINED`, passed as `--retained` flags; the
policy check requires 64-hex entries distinct from the current build. The
provisioning hook records each new build in `retained_builds` before the host
starts. Retiring an old build from publication is a separate, deliberate ADR-0068
barrier.
+16
View File
@@ -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.