fix(deploy-kernel): final-verify falls back to the durable in-cluster MANIFEST #2061

Merged

pipeline-bot merged 1 commit from fix/final-verify-incluster-fallback into trunk

2026-08-16 11:06:52 +00:00

sean commented

2026-08-16 11:06:03 +00:00

Owner

The sf34 workers roll converged 5/5 then failed final-verify on the quota-bounced codeberg MANIFEST (best-effort by design since 1d3670ee). Fallback to the durable pkg copy; the frozen release digest still decides.

The sf34 workers roll converged 5/5 then failed final-verify on the quota-bounced codeberg MANIFEST (best-effort by design since 1d3670ee). Fallback to the durable pkg copy; the frozen release digest still decides.

sean added 1 commit

2026-08-16 11:06:03 +00:00

fix(deploy-kernel): final-verify falls back to the durable in-cluster MANIFEST

pipeline/ci CI green @ 60b9e2f4c6a0

Details

60b9e2f4c6

1d3670ee made the codeberg snapshot-MANIFEST leg best-effort at release
time — quota/WAF/504 must never gate a kernel — but final-verify still
hard-required the recorded codeberg URI to SERVE. First real exercise:
the seanfarm34 workers roll converged all 5 nodes, then failed
final-verify on the quota-bounced backup (five 404s), producing an
honest fleet and a false Failed.

Availability now has two sources, integrity still one digest: try the
recorded codeberg URI, fall back to the durable pkg copy
(anonymous-download, no lifecycle rules) that the same release's
promote gate wrote. The frozen release digest decides in both paths, so
a wrong byte from either source still fails the roll.

pipeline-bot merged commit 60b9e2f4c6 into trunk

2026-08-16 11:06:52 +00:00

No reviewers

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

sean/pipelines!2061

No description provided.

Rows
Columns