Selenium grid nodes cannot connect to selenium grid hub across grid network

[mhagen-vmware]

docker network create grid docker run -d -p 4444:4444 --net grid --name selenium-hub selenium/hub:3.9.1 docker run -d --net grid -e HUB_HOST=selenium-hub --name chrome1 selenium/node-chrome:3.9.1

I am creating 15 of these nodes in my test, at least chrome3 and chrome10 succeeded: Z6jRzNa/IBVwBA==16:33:23.331 INFO - The node is registered to the hub and ready to use

But pretty much ever other one did not succeed: c5dCDInAIBVwCA==16:46:08.899 INFO - Couldn't register this node: The hub is down or not responding: selenium-hub: Temporary failure in name resolution 8hfTNorAIBUQBg==16:46:13.908 INFO - Couldn't register this node: The hub is down or not responding: selenium-hub

or AiL+EnDAIBXgCA==16:44:21.638 INFO - I/O exception (java.net.SocketException) caught when processing request to {}->http://selenium-hub:4444: Connection reset IwPfFHDAIBVQBA==16:44:21.646 INFO - Retrying request to {}->http://selenium-hub:4444 Dk0hjYHAIBVwCA==16:45:36.701 INFO - Couldn't register this node: The hub is down or not responding: selenium-hub: Temporary failure in name resolution 8VlLt4LAIBUQBg==16:45:41.704 INFO - Couldn't register this node: The hub is down or not responding: selenium-hub

container-logs.zip

[mhagen-vmware]

This appears to be related to slower storage. When I switched from a really small NFS server to a big iSCSI backed storage the test not only ran faster but started passing.

[lcastellano]

Closing as a dup of #7682

[Pacifique2]

Hi @mhagen-vmware , I am actually facing the same error when i try to register selenium chrome nodes to the selenium hub node. I am running them in a kubernetes cluster of 2 Raspberry Pi 3 B. Would you please suggest me any possible troubleshooting of this issue?