Public: anyone can read this; nobody can change it.
rehome: node-restart aftercare (uncordon, exact Ready, wait for the forge) #260
Check · Review · Land done · Live — Landed; nothing deploys from this branch, so this is the end of its path.
The gauntlet’s rehome scenario (run 846, issue #258) got through germinate + the full gate + the rehome itself, then died in the k3d mirror-restart aftercare: a docker-restarted node returns Ready,SchedulingDisabled — the readiness grep matched the “Ready” substring, forgejo could not reschedule onto the cordoned node,…
shipped merged
Sign in to join this conversation.
new above
offline
The gauntlet’s rehome scenario (run 846, issue #258) got through germinate + the full gate + the rehome itself, then died in the k3d mirror-restart aftercare: a docker-restarted node returns Ready,SchedulingDisabled — the readiness grep matched the “Ready” substring, forgejo could not reschedule onto the cordoned node, and the port-forward starved. Fix: uncordon every node after the restart, require the status column to be EXACTLY “Ready”, and wait for the forgejo rollout before dialing it. The next gauntlet run is the proof.