-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Closed as not planned
Labels
Description
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)
...
autoscaling:
enabled: true
scalingType: job
scalingStrategy:
strategy: default
chromeNode:
enabled: true
terminationGracePeriodSeconds: 3600
scaledOptions:
maxReplicaCount: 50
minReplicaCount: 0
extraEnvironmentVariables:
- name: SE_VNC_NO_PASSWORD
value: "true"
- name: SE_VNC_VIEW_ONLY
value: "true"
...Relevant log output
No relevant logs as far as I knowOperating System
Kubernetes
Docker Selenium version (image tag)
4.27.0 (revision d6e718d)
Selenium Grid chart version (chart version)
0.38.4