-
-
Notifications
You must be signed in to change notification settings - Fork 8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
[馃悰 Bug]: issue 9586 - still happening - version 4.20.0 - Unable to register node to OpenShift hub #13958
Comments
@e-dsouza, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
Hi, @e-dsouza. 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. |
@pujagani Thanks for your response. This is the command I ran to register node to hub 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. |
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 |
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 @KrzysztofC were you able to resolve this? |
The Hub does not reply with 5xx, it should be layer you have on top of it. |
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 |
4442 and 4443 are TCP, not HTTP. |
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 |
This isn't resolved yet. I'm still working with OCP admin team to assist with 502 gateway error. So far no positive outcome. |
What happened?
Unable to register node - hub in OCP pod, Node on windows server - image used - 4.20.0-20240505
Command run to register node:
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-xxx.apps.ocp4-xxx.xxxint.net:443
Stuck at INFO [NodeServer$1.lambda$start$1] - Sending registration event no info on Hub OCP Pod log
when you try curl on publish event OCP route, pointed to hub port 4442
C:>curl-i https://publish-events-xxx-xxx.apps.ocp4-xxx.xxxint.net
HTTP/1.1 502 Bad Gateway
content-length: 107
cache-control: no-cache
content-type: text/html
Set-Cookie: BIGipServerwildcard-apps-ocp4-xx-443=!N/xx+xx; path=/; Httponly; Secure
502 Bad Gateway
The server returned an invalid or incomplete response.
Curl within OCP hub Pod:
$ curl localhost:4444 -verbose
*Trying 127.0.0.1:4444...
*Connected to localhost (127.0.0.1) port 4444 (#0)
Mark bundle as not supporting multiuse
<HTTP/1.1 302 Found
<content-length:0
<Location: /ui/
<
*Connection #0 to host localhost left intact
$ curl localhost:4442 -verbose
Trying 127.0.0.1:4442...
Connected to localhost (127.0.0.1) port 4442 (#0)
Received HTTP/0.9 when not allowed
<
curl: (1) Received HTTP/0.9 when not allowed
$ curl localhost:4443-verbose Trying 127.0.0.1:4443...
Received HTTP/0.9 when not allowed**
Closing connection 0
curl: (1) Received HTTP/0.9 when not allowed
How can we reproduce the issue?
Relevant log output
Operating System
Windows 2022 server, Linux (OCP pod -hub)
Selenium version
4.20.0
What are the browser(s) and version(s) where you see this issue?
N/A
What are the browser driver(s) and version(s) where you see this issue?
N/A
Are you using Selenium Grid?
4.20.0-20240505
The text was updated successfully, but these errors were encountered: