TCP connection to localhost & DNS issues #26592
-
A few days ago I started seeing test failures resulting from a new DNS configuration in GH Action runners on ubuntu-latest. Whether you get the new or old DNS configuration is seemingly random with different jobs in the same workflow run getting different configurations. Test WorkflowHere’s a test workflow which checks the output of the shell oliver-sanders/actions-dns-test/blob/b9445721f206ab705fa2c50de1e53a534f1b53db/.github/workflows/test_dns.yml
This file has been truncated. show original Here’s an example of a working DNS configuration (for local TCP):
With this configuration it is possible to open a TCP connection to:
And here’s an example of a broken one (for local TCP):
With this configuration it is possible to open a TCP connection to
I’ve been successfully using GH actions to test an application that resolves hostnames from aliases and performs local TCP connections since May last year. This issue has only cropped up in the last week or so. Any thoughts or ideas? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
That looks like it might be related to this issue: github.com/actions/virtual-environmentsReverse name lookup is broken for current hostname in ubuntu-latest VMs
Description Reverse name lookup is broken for the current hostname. This leads to odd issues. Here are some reports from GitHub Community: https://github.community/t/github-action-and-oserror-errno-99-cannot-assign-requested-address/173973 https://github.community/t/volatile-local-ip-addresses-during-action-run/174362 https://github.community/t/github-actions-timeout/174533 This...
Area: Common Tools
OS: Ubuntu
investigate
|
Beta Was this translation helpful? Give feedback.
That looks like it might be related to this issue:
github.com/actions/virtual-environmentsReverse name lookup is broken for current hostname in ubuntu-latest VMs