ctubbsii commented on issue #2016: URL: https://github.com/apache/accumulo/issues/2016#issuecomment-820773438
Okay, so I've spent a few hours looking into this today, and I think it's a bug in GitHub Actions DNS servers. If you create a GitHub Actions job that simply prints the output of `hostname -i` and `hostname -I`, you can clearly see there's a problem. They don't return the same IP address. The former uses DNS to show the IP address based on the current machine's hostname. The latter shows the IP addresses for the non-loopback network interfaces on the current machine. The IP address from the DNS lookup does not match any of the network interfaces for this machine. So, clearly, something is wrong. You can confirm the local network interfaces with `ifconfig` or `ip -4 -br addr`. Since Accumulo services are listening on `0.0.0.0`, and using `hostname` to advertise themselves in ZooKeeper, and since `hostname` results in an IP address resolution that doesn't match any of the IP addresses for any of the local network interfaces on the current machine, of course it can't talk to the Accumulo process.... because it's using the wrong IP address! I tried a few different methods to force the name lookup to resolve correctly, including using `myhostname` entry in `/etc/nsswitch.conf` prior to `files dns`, I tried dropping `dns` from that as well, and I tried appending an entry in `/etc/hosts` with the correct IP address for the current host. All of these are hacks, and nothing seemed to work quite right. Another workaround would be to force minicluster services to listen on `localhost`/`127.0.0.1`. This isn't a great solution, but it might resolve the problems with misconfigured DNS in GitHub Actions runners. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
