-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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]: Selenium Grid 4.20.0 not fetching node after some time #2236
Comments
@Amanyadav12345, 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! |
How can we reproduce the issue? You are sharing zero details on how you deploy the Grid. |
@Amanyadav12345, have you deployed on K8s or docker compose? |
What happened?
We can see 504 errors on the grid setup
and if we rerun the hub then it's coming to normal for some time and does the same thing again
no logs are there for tracing in hub-nodes logs
Command used to start Selenium Grid with Docker (or Kubernetes)
Relevant log output
Operating System
Windows server 2016 datacenter
Docker Selenium version (image tag)
4.20.0
Selenium Grid chart version (chart version)
4.20.0
The text was updated successfully, but these errors were encountered: