Immutable solution version
Unable to obtain: Capabilities -> Issue still present in 4.15
Complete solution
How to fix unable to obtain: Capabilities -> Issue still present in 4.15 (Selenium). The verified answer from the upstream issue, distilled into steps.
Unable to obtain: Capabilities -> Issue still present in 4.15
What was going on Issue SeleniumHQ/selenium#13091 (closed, 90 comments): ### What happened?
Occasionally in our tests we get this error. I can't see any thing special that happens, it is just that sometimes we cant get a session from the grid.
Our setup is like: Kubernetes for 1 hub with selenium/hub:4.15 4 Nodes based on selenium/node-base:4.15 all with different capabilities (3 nodes with mtls certs inserted and 1 node "vanilla")
All nodes have "manually installed" browsers as in we install chrome, edge and firefox it in the dockerfile.
All nodes are setup with this config:
[node]
session-timeout = "300"
override-max-sessions =...
The fix
If Grid 4.15 intermittently fails with 'Unable to obtain: Capabilities', use the 4.15.0-20231122 docker images or newer. That release sets the browser driver path via properties and avoids Selenium Manager, which a reporter confirmed fixed the problem.Evidence
In gh:SeleniumHQ/selenium#13091 the issue was: Issue SeleniumHQ/selenium#13091 (closed, 90 comments): ### What happened?
Occasionally in our tests we get this error. I can't see any thing special that happens, it is just that sometimes we cant get a session from the grid.
Our setup is like: Kubernetes for 1 hub with selenium/hub:4.15 4 Nodes based on selenium/node-base:4.15 all with different capabilities (3 nodes with mtls certs inserted and 1 node "vanilla")
All nodes have "manually installed" browsers as in we install chrome, edge and firefox it in the dockerfile.
All nodes are setup with this config:
[node]
session-timeout = "300"
override-max-sessions =... The verified answer: If Grid 4.15 intermittently fails with 'Unable to obtain: Capabilities', use the 4.15.0-20231122 docker images or newer. That release sets the browser driver path via properties and avoids Selenium Manager, which a reporter confirmed fixed the problem. Source: https://github.com/SeleniumHQ/selenium/issues/13091By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl__7GChqcVqc82RGl_2m77xA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Unable to obtain: Capabilities -> Issue still present in 4.15 <span>— Vectle</span></a>