You are viewing a plain text version of this content. The canonical link for it is here.

Posted to builds@apache.org by Lari Hotari <la...@sagire.fi> on 2021/04/14 15:16:57 UTC

GitHub Actions: Reverse DNS lookup for current hostname is broken, causes network issues

Hi all,

Reverse DNS lookups for the current hostname is broken on ubuntu-latest
GitHub Actions Runner VMs.
The reverse lookup returns different IP addresses which aren't addresses of
the current host.
This can cause various networking issues.

The workaround is to add an entry for the host name to /etc/hosts.

For example, by adding this action in the workflow's build job:

- name: Add the current IP address, long hostname and short hostname record
to /etc/hosts file
  run: |
     echo -e "$(ip addr show eth0 | grep "inet\b" | awk '{print $2}' | cut
-d/ -f1)\t$(hostname -f) $(hostname -s)" | sudo tee -a /etc/hosts

More information:
Apache Pulsar issue:
https://github.com/apache/pulsar/issues/10232
Apache Pulsar fix (currently in-progress):
https://github.com/apache/pulsar/pull/10233

I did a quick search on GitHub Community site and found these problem
reports:

   -
   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

I hope this helps.

BR,

Lari

Re: GitHub Actions: Reverse DNS lookup for current hostname is broken, causes network issues

Posted by Christopher Tubbs <ct...@apache.org>.

I saw the same thing and filed a bug report with GitHub (https://support.github.com/ticket/1108915)
They replied that they were able to reproduce the issue.
I worked around it with: https://github.com/apache/accumulo/commit/1dc21016654dc4d8a66178540fe2ce8012deb5be

On 2021/04/14 15:16:57, Lari Hotari <la...@sagire.fi> wrote: 
> Hi all,
> 
> Reverse DNS lookups for the current hostname is broken on ubuntu-latest
> GitHub Actions Runner VMs.
> The reverse lookup returns different IP addresses which aren't addresses of
> the current host.
> This can cause various networking issues.
> 
> The workaround is to add an entry for the host name to /etc/hosts.
> 
> For example, by adding this action in the workflow's build job:
> 
> - name: Add the current IP address, long hostname and short hostname record
> to /etc/hosts file
>   run: |
>      echo -e "$(ip addr show eth0 | grep "inet\b" | awk '{print $2}' | cut
> -d/ -f1)\t$(hostname -f) $(hostname -s)" | sudo tee -a /etc/hosts
> 
> More information:
> Apache Pulsar issue:
> https://github.com/apache/pulsar/issues/10232
> Apache Pulsar fix (currently in-progress):
> https://github.com/apache/pulsar/pull/10233
> 
> I did a quick search on GitHub Community site and found these problem
> reports:
> 
>    -
>    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
> 
> I hope this helps.
> 
> BR,
> 
> Lari
>