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.