You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We just upgraded from Helm chart 0.37.4 to 0.38.4, and with the new version, Selenium now seems to think that our autoscaling chrome node containers are running Windows, when they are in fact running Linux. For us, this just amounts to a visual bug where the sessions UI incorrectly shows the Windows logo instead of Tux, since nobody at our organization has capabilities requesting a specific platform, but I guess it could cause bigger problems for anyone who's actually creating capabilities that need specific operating systems.
Note for security reasons I cannot provide the full YAML configuration, but I have included the relevant bits related to the autoscaler and chromeNode.
Command used to start Selenium Grid with Docker (or Kubernetes)
@isc-aray, thank you for creating this issue. We will troubleshoot it as soon as we can.
Info for maintainers
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.
Don't worry, it will be fixed in Grid core 4.28.0 via SeleniumHQ/selenium#15036
To get the right Linux icon on Grid UI, you can explicit provide the platformName in each node config. For example
What happened?
We just upgraded from Helm chart 0.37.4 to 0.38.4, and with the new version, Selenium now seems to think that our autoscaling chrome node containers are running Windows, when they are in fact running Linux. For us, this just amounts to a visual bug where the sessions UI incorrectly shows the Windows logo instead of Tux, since nobody at our organization has capabilities requesting a specific platform, but I guess it could cause bigger problems for anyone who's actually creating capabilities that need specific operating systems.
Note for security reasons I cannot provide the full YAML configuration, but I have included the relevant bits related to the autoscaler and chromeNode.
Command used to start Selenium Grid with Docker (or Kubernetes)
Relevant log output
Operating System
Kubernetes
Docker Selenium version (image tag)
4.27.0 (revision d6e718d)
Selenium Grid chart version (chart version)
0.38.4
The text was updated successfully, but these errors were encountered: