Repository navigation
e2e: use a port-forward per router CONNECT tunnel - #3051
Merged
Haven Xia (HavenXia) merged 2 commits intoOct 22, 2026
Merged
Haven Xia (HavenXia) merged 2 commits into
Haven Xia (HavenXia) merged 2 commits into
Conversation
Benjamin Elder (BenTheElder)
requested review from
Eitan Yarmush (EItanya) and
Keith Mattix II (keithmattix)
October 21, 2026 11:36
Benjamin Elder (BenTheElder)
requested a review
from Dmitry Berkovich (dberkov)
October 22, 2026 09:06
Dmitry Berkovich (dberkov)
previously approved these changes
Oct 22, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Oct 22, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Oct 22, 2026
Collaborator
Author
|
build started failing in the queue? must be a logical conflict in main, looking |
client-go closes the whole port-forward when any connection on it errors, so a reset on one tunnel broke every Connect after it
Collaborator
Benjamin Elder (BenTheElder)
force-pushed
the
e2e-connect-portforward-per-conn
branch
from
October 22, 2026 20:18
089f1cd to
25dbab8
Compare
Collaborator
Author
|
should be fixed |
Haven Xia (HavenXia)
approved these changes
Oct 22, 2026
Benjamin Elder (BenTheElder)
deleted the
e2e-connect-portforward-per-conn
branch
October 24, 2026 01:51
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TestActorArbitraryPortAccess has been flaking in e2e since the router moved to static-mtls in #2390, e.g. https://github.com/agent-substrate/substrate/actions/runs/39549120410/job/119054007125
client-go closes the whole port-forward when any one connection on it errors:
https://github.com/kubernetes/client-go/blob/v0.37.0/tools/portforward/portforward.go#L549-L550
RouterClient shared one CONNECT port-forward for the life of the client. So one reset from the router failed the tunnel in flight and every Connect after it, which then got "connection refused" from the dead local port. #2961 fixed the same thing in ingressauth by forwarding per attempt.
Why is this needed? (Or link the issue. Open one first for features, API, install or CI changes.)
Fixes a trivial test flake bug, test only change. Spotted while reviewing PRs like #2502
AI use: AI-assisted, I reviewed it.