[🐛 Bug]: issue 9586 - still happening - version 4.20.0 - Unable to register node to OpenShift hub

[e-dsouza]

[🐛 Bug]: issue 9586 - still happening - version 4.20.0 - Unable to register node to OpenShift hub

[diemol]

You should run the Hub and the Nodes in debug mode to understand missing information. The Node sends a message through the event bus, so you need to see that message incoming and being read by the Hub. Then, the Hub will make an HTTP call to the Node to confirm its existence.

This issue happens when network permissions are not properly set, which ends up as HTTP/1.1 502 Bad Gateway

[github-actions]

@e-dsouza, 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!

[github-actions]

Hi, @e-dsouza.
Please follow the issue template, we need more information to reproduce the issue.

Either a complete code snippet and URL/HTML (if more than one file is needed, provide a GitHub repo and instructions to run the code), the specific versions used, or a more detailed description to help us understand the issue.

Note: If you cannot share your code and URL/HTML, any complete code snippet and URL/HTML that reproduces the issue is good enough.

Reply to this issue when all information is provided, thank you.

[e-dsouza]

@pujagani Thanks for your response.

This is the command I ran to register node to hub
java -jar selenium-server-4.20.0.jar node --publish-events tcp://publish-events-xxx-xxx.apps.ocp4-xxx.xxxint.net:443 --subscribe-events tcp://subscribe-events-xxx- xxxx.apps.ocp4-xxx.xxxint.net:443

I do not have any github repo/code, I am trying to setup Grid. Hub is running as Openshift Pod. Now trying to add windows server 2022 as node

my issue is exactly same as issue 9586

Thanks for your time.

[e-dsouza]

Okay, I'll have to check OCP team, I believe, how to run container in debug mode.

My guess is that the OCP route isnt getting right response from hub so it is giving 502 Bad gatway error, see below when I do curl within the OCP Pod.

$ curl localhost:4442 -verbose
Trying 127.0.0.1:4442...
Connected to localhost (127.0.0.1) port 4442 (#0)
GET/HTTP/1.1
Host: localhost:4442
User-Agent: curl/7.81.0
Accept: /
Received HTTP/0.9 when not allowed

@KrzysztofC were you able to resolve this?

[diemol]

The Hub does not reply with 5xx, it should be layer you have on top of it.

[e-dsouza]

Okay. it doesnt give 5xx but should it not give valid one? again I am just guessing 000 converted to 502 by route

$ curl -o /dev/null -s -w "%{http.code}\n" localhost:4442
000
$ curl -o/dev/null -s -w "%{http code}\n" localhost:4444
302
$ curl -o /dev/null -s -w "%{http_code}\n" localhost:4443
000

[diemol]

4442 and 4443 are TCP, not HTTP.

[e-dsouza]

Okay, I may need to check OCP route?

My command is doing TCP using route url

java -jar selenium-server-4.20.0.jar node --publish-events tcp://publish-events-xxxx-xxxx.apps.ocp4-

xxx.xxxint.net:443 --subscribe-events tcp://subscribe-events-xxx-xxxx.apps.ocp4-xxxx.xxxint.net:443

[e-dsouza]

This isn't resolved yet. I'm still working with OCP admin team to assist with 502 gateway error. So far no positive outcome.