[v3-2-test] Move jaeger CI host ports below ephemeral range to fix flake (#65867) by github-actions[bot] · Pull Request #65868 · apache/airflow

github-actions · 2026-04-26T11:55:06Z

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

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

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

github-actions · 2026-04-26T11:55:06Z

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

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

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

github-actions · 2026-04-26T11:55:06Z

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

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

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

github-actions · 2026-04-26T11:55:06Z

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

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

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

github-actions · 2026-04-26T11:55:06Z

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

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

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

github-actions · 2026-04-26T11:55:06Z

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

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

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

github-actions · 2026-04-26T11:55:06Z

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

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

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

github-actions · 2026-04-26T11:55:06Z

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

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

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

github-actionsBot mentioned this pull request Apr 26, 2026
Move jaeger CI host ports below ephemeral range to fix flake #65867
Merged
1 task

boring-cyborgBot added the area:dev-tools label Apr 26, 2026

potiuk marked this pull request as ready for review April 26, 2026 12:09

potiuk requested review from amoghrajesh, ashb, bugraoz93, gopidesupavan, jason810496, jscheffl and potiuk as code owners April 26, 2026 12:09

potiuk force-pushed the backport-c29cc61-v3-2-test branch from be3fd3c to d943e64Compare April 26, 2026 16:59

potiuk merged commit e5e938a into v3-2-testApr 26, 2026
110 checks passed

potiuk deleted the backport-c29cc61-v3-2-test branch April 26, 2026 19:45

vatsrahul1001 added the changelog:skip Changes that should be skipped from the changelog (CI, tests, etc..) label May 18, 2026

vatsrahul1001 added this to the Airflow 3.2.2 milestone May 18, 2026