Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using the --proxy-via flag would sometimes cause connection timeouts. #3786

Merged
merged 5 commits into from
Feb 4, 2025

Conversation

thallgren
Copy link
Member

Typically, a telepresence connect --proxy-via <subnet>=<workflow>
would fail with a "deadline exceeded" message when several workloads
were present in the namespace, the one targeted by the proxy-via didn't
yet have an agent installed, and other workloads had an agent. This was
due to a race condition in the logic for the agent-based port-forwards
in the root daemon. The conditions causing this race are now eliminated.

@thallgren thallgren linked an issue Feb 2, 2025 that may be closed by this pull request
@thallgren thallgren requested review from P0lip, FuYu3699 and njayp February 2, 2025 15:13
@thallgren thallgren added the ok to test Applied by maintainers when a PR is ready to have tests run on it label Feb 2, 2025
@github-actions github-actions bot removed the ok to test Applied by maintainers when a PR is ready to have tests run on it label Feb 2, 2025
@thallgren thallgren force-pushed the thallgren/proxy-via-multi-wf branch 2 times, most recently from 84b327a to 92133b4 Compare February 2, 2025 22:58
Typically, a `telepresence connect --proxy-via <subnet>=<workflow>`
would fail with a "deadline exceeded" message when several workloads
were present in the namespace, the one targeted by the proxy-via didn't
yet have an agent installed, and other workloads had an agent. This was
due to a race condition in the logic for the agent-based port-forwards
in the root daemon. The conditions causing this race are now eliminated.

Signed-off-by: Thomas Hallgren <[email protected]>
Signed-off-by: Thomas Hallgren <[email protected]>
@thallgren thallgren force-pushed the thallgren/proxy-via-multi-wf branch from 92133b4 to 1f733e7 Compare February 2, 2025 23:15
@thallgren thallgren added the ok to test Applied by maintainers when a PR is ready to have tests run on it label Feb 2, 2025
@github-actions github-actions bot removed the ok to test Applied by maintainers when a PR is ready to have tests run on it label Feb 2, 2025
@thallgren thallgren force-pushed the thallgren/proxy-via-multi-wf branch from 8ecec22 to 0566da4 Compare February 3, 2025 06:38
@thallgren thallgren added the ok to test Applied by maintainers when a PR is ready to have tests run on it label Feb 3, 2025
@github-actions github-actions bot removed the ok to test Applied by maintainers when a PR is ready to have tests run on it label Feb 3, 2025
Base automatically changed from thallgren/v2.21.3 to release/v2.21 February 3, 2025 06:40
@thallgren thallgren merged commit 7986105 into release/v2.21 Feb 4, 2025
11 checks passed
@thallgren thallgren deleted the thallgren/proxy-via-multi-wf branch February 4, 2025 15:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Potential race condition in connect with --proxy-via parameter
2 participants