Open rohithkk opened 1 week ago
@rohithkk, thank you for creating this issue. We will troubleshoot it as soon as we can.
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!
org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Response code 500. Message: Could not start a new session. No nodes support the capabilities in the request
What are the capabilities set in your tests? Is managed downloads enabled in test and also --enable-managed-downloads
enabled in Node config?
@VietND96 I do not have any custom desired capabilities set. I have posted the code snippet for starting a new chrome driver session.
The stacktrace also shows all the "capabilities" that are being requested.
org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Response code 500. Message: Could not start a new session. No nodes support the capabilities in the request
..............................
Command: [null, newSession {capabilities=[Capabilities {browserName: chrome, goog:chromeOptions: {args: [--headless=new, --incognito, --no-sandbox, --disable-gpu, --disable-dev-shm-usage], extensions: []}}]}]
Capabilities {browserName: chrome, goog:chromeOptions: {args: [--headless=new, --incognito, --no-sandbox, --disable-gpu, --disable-dev-shm-usage], extensions: []}}
In logs, that is browser options. Did you set any other caps that have prefix se:
or in generic format key:value
?
@VietND96 the only se
option is the SE_CACHE_PATH
environment variable set to /tmp/selenium
. No other SE
flags set.
Env var SE_CACHE_PATH
is not used anywhere. Do you refer to which docs for this?
I have removed that variable but it didn't help. Still running into same issue
What happened?
We have automation tests using Selenium framework that run on Docker container during CI/CD process. We have dependency on
org.seleniumhq.selenium:selenium-java:4.15.0
and use the Devtools API to capture network trace and request/responses. We are using classes fromorg.openqa.selenium.devtools.v117.*
package.This logic works perfectly fine when running the tests on docker container with the image
selenium/standalone-chrome:117.0-20231004
.I'm trying to update the selenium and docker image version. I chose the latest available version selenium library
org.seleniumhq.selenium:selenium-java:4.26.0
and the docker image asselenium/standalone-chrome:130.0-20241101
. But this time, the tests fail to run since the Chrome session cannot be created. Code for creating webdriver instance is straightforward.Relevant log output
Operating System
Kubernetes
Docker Selenium version (image tag)
selenium/standalone-chrome:130.0-20241101
Selenium Grid chart version (chart version)
No response