[🐛 Bug]: Could not determine if the address is IPv6 or IPv4

[Doofus100500]

What happened?

distributor does not start

Command used to start Selenium Grid with Docker (or Kubernetes)

helm

Relevant log output

{"class": "UnboundZmqEventBus","log-level": "WARNING","log-message": "Could not determine if the address tcp:\u002f\u002fselenium-grid-selenium-event-bus.selenium-test.svc.cluster.local:4442 is IPv6 or IPv4","log-name": "org.openqa.selenium.events.EventBus","log-time-local": "2025-01-15T13:08:14.827Z","log-time-utc": "2025-01-15T13:08:14.827Z","method": "isSubAddressIPv6"}
13:08:14.830 WARN [UnboundZmqEventBus.lambda$new$3] - Connecting to tcp://selenium-grid-selenium-event-bus.selenium-test.svc.cluster.local:4442 and tcp://selenium-grid-selenium-event-bus.selenium-test.svc.cluster.local:4443 failed
{"class": "UnboundZmqEventBus","log-level": "WARNING","log-message": "Connecting to tcp:\u002f\u002fselenium-grid-selenium-event-bus.selenium-test.svc.cluster.local:4442 and tcp:\u002f\u002fselenium-grid-selenium-event-bus.selenium-test.svc.cluster.local:4443 failed","log-name": "org.openqa.selenium.events.EventBus","log-time-local": "2025-01-15T13:08:14.83Z","log-time-utc": "2025-01-15T13:08:14.83Z","method": "lambda$new$3"}
13:08:20.551 WARN [UnboundZmqEventBus.lambda$new$4] - Failure #3. Retrying.
{"class": "UnboundZmqEventBus","log-level": "WARNING","log-message": "Failure #3. Retrying.","log-name": "org.openqa.selenium.events.EventBus","log-time-local": "2025-01-15T13:08:20.551Z","log-time-utc": "2025-01-15T13:08:20.551Z","method": "lambda$new$4"}
13:08:20.552 WARN [UnboundZmqEventBus.isSubAddressIPv6] - Could not determine if the address tcp://selenium-grid-selenium-event-bus.selenium-test.svc.cluster.local:4442 is IPv6 or IPv4

Operating System

k8s

Docker Selenium version (image tag)

4.27.0-20250101

Selenium Grid chart version (chart version)

0.38.4

[github-actions]

@Doofus100500, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[VietND96]

It looks like your cluster is using another DNS for svc, which is not *.svc.cluster.local?

[Doofus100500]

That's right:

cat /etc/resolv.conf
search selenium-test.svc.staging-cl1 svc.staging-cl1 staging-cl1 default.svc.staging-cl1
nameserver 10.233.0.3
nameserver 10.233.0.5
options ndots:3 attempts:5 timeout:2

What can i do to fix?

[VietND96]

In an update, I added *.svc.cluster.local to all svc DNS. Since I believe any cluster should have this kind of DNS record. So, is this incorrect?

[Doofus100500]

It turns out that this is not the case everywhere. I checked all the clusters where my grid operates, and everywhere the situation is as I described above.

[VietND96]

The fix in chart version 0.38.5.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.