[v3-2-test] Move jaeger CI host ports below ephemeral range to fix flake (#65867)#65868
Merged
Conversation
1 task
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
gopidesupavan,
jason810496,
jscheffl and
potiuk
as code owners
…ake (#65867) The jaeger container in the otel integration compose file mapped four host ports (34317, 34318, 36686, 39422) inside the Linux default ephemeral port range (32768-60999). The kernel can transiently grab a port in that range as the source port of an outbound connection from any other process on the CI runner, which then races with the docker bind and surfaces as: failed to bind host port for 0.0.0.0:34318:172.18.0.3:4318/tcp: address already in use The retry mechanism (which restarts docker between attempts) does not help, because the holder is a non-docker process. Move the four jaeger host ports below 32768, matching the convention the other integration services in the same file already follow, and update the docstring in test_otel.py that pointed at the old jaeger UI port. (cherry picked from commit c29cc61) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
potiuk
force-pushed
the
backport-c29cc61-v3-2-test
branch
from
be3fd3c to
d943e64
Compare
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 27, 2026
…ake (#65867) (#65868) The jaeger container in the otel integration compose file mapped four host ports (34317, 34318, 36686, 39422) inside the Linux default ephemeral port range (32768-60999). The kernel can transiently grab a port in that range as the source port of an outbound connection from any other process on the CI runner, which then races with the docker bind and surfaces as: failed to bind host port for 0.0.0.0:34318:172.18.0.3:4318/tcp: address already in use The retry mechanism (which restarts docker between attempts) does not help, because the holder is a non-docker process. Move the four jaeger host ports below 32768, matching the convention the other integration services in the same file already follow, and update the docstring in test_otel.py that pointed at the old jaeger UI port. (cherry picked from commit c29cc61) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
vatsrahul1001
added
the
changelog:skip
vatsrahul1001
pushed a commit
that referenced
this pull request
May 20, 2026
…ake (#65867) (#65868) The jaeger container in the otel integration compose file mapped four host ports (34317, 34318, 36686, 39422) inside the Linux default ephemeral port range (32768-60999). The kernel can transiently grab a port in that range as the source port of an outbound connection from any other process on the CI runner, which then races with the docker bind and surfaces as: failed to bind host port for 0.0.0.0:34318:172.18.0.3:4318/tcp: address already in use The retry mechanism (which restarts docker between attempts) does not help, because the holder is a non-docker process. Move the four jaeger host ports below 32768, matching the convention the other integration services in the same file already follow, and update the docstring in test_otel.py that pointed at the old jaeger UI port. (cherry picked from commit c29cc61) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
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
2 participants
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.
The jaeger container in the otel integration compose file mapped four
host ports (34317, 34318, 36686, 39422) inside the Linux default
ephemeral port range (32768-60999). The kernel can transiently grab a
port in that range as the source port of an outbound connection from
any other process on the CI runner, which then races with the docker
bind and surfaces as:
failed to bind host port for 0.0.0.0:34318:172.18.0.3:4318/tcp:
address already in use
The retry mechanism (which restarts docker between attempts) does not
help, because the holder is a non-docker process.
Move the four jaeger host ports below 32768, matching the convention
the other integration services in the same file already follow, and
update the docstring in test_otel.py that pointed at the old jaeger UI
port.
(cherry picked from commit c29cc61)
Co-authored-by: Jarek Potiuk jarek@potiuk.com