Public: anyone can read this; nobody can change it.

azure-gate: pkill only the kubectl port-forward, not the gate's own shell #156

Merged opened this view on origin

Check · Review · Land done · Live — Landed; nothing deploys from this branch, so this is the end of its path.

Merged

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 -…

Notes

shipped merged

opened this view on origin

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:

COLDSTART GATE PASS ( 63s): all assertions passed (...domain=172-174-30-171.sslip.io...)
==> gate: FATAL: coldstart gate FAILED on 172-174-30-171.sslip.io
Connection to 172.174.30.171 closed by remote host.

Cause: run_gate's post-assert reap ran pkill -f "port-forward svc/forgejo-http", but that pattern string is present in the SSH bash -c command's own argv, so pkill killed its own parent shell → the SSH channel dropped (exit 255) → the gate read non-zero and died. Fix: match kubectl.*port-forward svc/forgejo-http so 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

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs