fix(deploy-kernel): the stage assert accepts an already-booted target #2062

Merged
pipeline-bot merged 1 commit from fix/kstage-idempotent into trunk 2026-08-16 19:25:08 +00:00
Owner

status.staged is null on an already-converged node (bootc: Image specification is unchanged); the retried sf35 leg crashed on the None while the fleet was 5/5 on target. Accept staged OR booted matching the frozen digest; three-state simulation attached in the commit.

status.staged is null on an already-converged node (bootc: Image specification is unchanged); the retried sf35 leg crashed on the None while the fleet was 5/5 on target. Accept staged OR booted matching the frozen digest; three-state simulation attached in the commit.
fix(deploy-kernel): the stage assert accepts an already-booted target
All checks were successful
pipeline/ci CI green @ 578b3b86c19e
578b3b86c1
'bootc switch' answers 'Image specification is unchanged' and stages
NOTHING when the node already runs the target — status.staged is null
and the assert crashed on the None ('NoneType' object is not
subscriptable). A retried roll-node leg after a completed stage+reboot
lands exactly there: the seanfarm35 workers roll converged 5/5 and
still recorded Failed on worker a40389.

The assert now accepts the digest in EITHER status.staged or
status.booted, and names both images when neither matches. Verified
against all three simulated bootc states (staged / booted / neither).
Sign in to join this conversation.
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!2062
No description provided.