Public: anyone can read this; nobody can change it.
azure-gate: pkill only the kubectl port-forward, not the gate's own shell #156
Check · Review · Land done · Live — Landed; nothing deploys from this branch, so this is the end of its path.
The vms gate reached the finish line — all cold-start assertions PASSED ("COLDSTART GATE PASS: all assertions passed") — but then falsely reported FAILED and tore down a healthy platform: Cause: rungate's post-assert reap ran pkill -f "port-forward svc/forgejo-http", but that pattern string is present in the SSH bash -…
shipped merged
Sign in to join this conversation.
new above
offline
The vms gate reached the finish line — all cold-start assertions PASSED ("COLDSTART GATE PASS: all assertions passed") — but then falsely reported FAILED and tore down a healthy platform:
Cause:
run_gate's post-assert reap ranpkill -f "port-forward svc/forgejo-http", but that pattern string is present in the SSHbash -ccommand's own argv, so pkill killed its own parent shell → the SSH channel dropped (exit 255) → the gate read non-zero anddied. Fix: matchkubectl.*port-forward svc/forgejo-httpso only the real kubectl process is reaped, never the gate's shell.This is the last blocker — deploy → germinate → assert all pass now; this makes the gate report the pass instead of a false failure.
🤖 Generated with Claude Code