[🐛 Bug]: invalid session id after upgrading to 4.15 (helm-charts on k8s) #2039
Labels
Comments
|
@cr-liorholtzman, 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! |
|
This is my values file: |
|
The router logs is also full of these: |
|
Hi @cr-liorholtzman, the same YAML that you used, can you have a try with chart version |
|
@VietND96 any idea why I'm not able to pull the image in the 0.25.3 chart?
|
|
Hi @cr-liorholtzman, it is due to feature was added recently in 0.25.3. The imageName: selenium/hub is split to 2 parts are imageRegistry: selenium and imageName: hub |
|
@VietND96 Thanks made the changes and update to 0.25.3, but still getting the same errors :/ Everything is ok once I revert back to 4.10 (chart 0.19) |
|
One thing I saw in router logs |
|
Yea it's because I switched the selenium version in the pom.xml to test both versions in the client as well, issue was happening with both clients version (while the hub version stayed the same - 4.15) |
|
Yes, but may I know is this failure happened on parallel test executions or it's a single test failed immediately? |
|
@VietND96 Hi, I can confirm it happens only when running tests in parallel. single tests do not fail. |
|
If it only happens in parallel, it is primarily an issue with how you do parallelization, and you are probably reusing the WebDriver variable. If you need help figuring out that part, use the links below to ask questions or join the Selenium Slack community. |
|
💬 Please ask questions at:
|
|
@diemol but it only happens after I upgrade from 4.10 to 4.15, it works perfectly well in 4.10. |
|
Then please share a code snippet we can use to reproduce the issue. In theory it should be reproducible against any Grid. When that is available, I'd be happy to reopen the issue. |
|
Hi @cr-liorholtzman, you mentioned that the upgrade from
|
|
@VietND96 tnx for that info. I did deploy with 0.19 chart. |
|
@cr-liorholtzman I think let's try to set it to I think you can override that via each node chromeNode:
extraEnvironmentVariables:
- name: DRAIN_AFTER_SESSION_COUNT
value: "0" |
|
@VietND96 Just to understand, so when will the pod get drained? |
|
@VietND96 btw it didn't help tested it now :/ |
|
@cr-liorholtzman where can I see the code snippet to reproduce the issue? You should also share the Grid logs, not the client logs. |
|
@diemol regarding the code I'm still working on it can share the entire project so trying to build something that can be shared and will reproduce the issue. Regarding the logs, I did :) these are the router logs I shared: |
|
That is not helpful because it only shows the error, not what happens before the error which is more helpful. We also need to see the Distributor and Node logs. |
|
@hi @diemol , Here are the logs, I'm afraid that I don't see any relevant errors in the Distributor or Note logs This is the error I get in the client On the Distributor side I see the session created but nothing else more relevant to it In the node logs again I see the session creation but nothing more: Strangely, I now can't see any errors in the router logs, just the start of the pod. |
|
When can you share the test code? |
|
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What happened?
After upgrading from 4.10 (chart version 19.0) to 4.15 (chart version 0.25.1) I started to get the following error that fails almost all UI tests - invalid session id
We run on a k8s cluster in GKE with KEDA installed (version 2.12.0).
Command used to start Selenium Grid with Docker (or Kubernetes)
"helm install $NAMESPACE docker-selenium/$NAMESPACE --namespace $NAMESPACE -f $VALUES_FILE --version 0.25.1 --set firefoxNode.enabled=false --set edgeNode.enabled=false"Relevant log output
Operating System
gke
Docker Selenium version (tag or chart version)
4.15.0-20231129
The text was updated successfully, but these errors were encountered: