-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[🐛 Bug]: 504 Gateway Time-out for Selenium Grid sessions #1808
Comments
@johnqa, 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! |
That 504 seems to come from ngnix, which Grid does not have. I assume you have that layer on top and you need to adjust the timeout there. |
Thank you, indeed it seemes to be an issue outside Selenium Grid. The timeout on the ingress controller of Kubernetes cluster was set to 60 seconds. By making it higher I have no more 504 errors. Basically I added this annotation to the nginx ingress: |
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. |
What happened?
Hi,
I am trying to run some selenium tests with Selenium Grid deployed in a Kubernetes cluster.
I have noticed some random errors regarding the sessions so in order to have a proper way of reproducing them, I set a scale of 1 for Chrome browser and having the browser pod restarting after every session.
What I notice now is that after some (usually just 1) successful sessions being executed, the sessions existing in the queue are failing when trying to connect to browser pod with 504 Gateway Time-out.
I have tried with both c# and python clients and also on Firefox and with countless configs. Same issue in every case.
I am running the python script (attached) like this:
python -m pytest -n 3 --reruns 3 ./webdriver_test.py
webdriver_test.py.txt
Command used to start Selenium Grid with Docker
Relevant log output
Operating System
RedHat
Docker Selenium version (tag)
4.8.1-20230306
The text was updated successfully, but these errors were encountered: