-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[🐛 Bug]: Firefox Blank or White Screen in OpenShift Container Platform when runnung exeutions #2273
Comments
@varsha-rav, 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! |
Hi any update one this? |
Hi @varsha-rav, in your case, the Grid is deployed by sys-admin, and as user/client, you don't have permission to do the workaround, right? |
Hi @VietND96 thats correct, we do not have the permissions to apply the workaround in client env |
This issue is looking for contributors. Please comment below or reach out to us through our IRC/Slack/Matrix channels if you are interested. |
@varsha-rav can you try new node Firefox image 4.24.0-20240907 and confirm. In this image, Firefox is installed to /home/seluser/firefox |
What happened?
Hi,
We've set up selenium 4 hub along with selenium/node-firefox, selenium/node-chrome and selenium/node-edge. On running executions on selenium/node-firefox, we're noticing a blank screen as below
The below issue shows that adding allowPrivilegeEscalation: true is the fix but we have limited privileges in client environment and this permission is not allowed
https://github.com/SeleniumHQ/docker-selenium/issues/1786
Is there any alternative to fix this issue or any update on this bug?
PS: Executions on edge and chrome are working as expected
Command used to start Selenium Grid with Docker (or Kubernetes)
containers: - resources: limits: cpu: 700m memory: 850Mi requests: cpu: 700m memory: 850Mi terminationMessagePath: /dev/termination-log name: selenium-firefox env: - name: SE_EVENT_BUS_HOST valueFrom: configMapKeyRef: name: seleniumhub key: SE_EVENT_BUS_HOST - name: SE_EVENT_BUS_PUBLISH_PORT valueFrom: configMapKeyRef: name: seleniumhub key: SE_EVENT_BUS_PUBLISH_PORT - name: SE_EVENT_BUS_SUBSCRIBE_PORT valueFrom: configMapKeyRef: name: seleniumhub key: SE_EVENT_BUS_SUBSCRIBE_PORT - name: SE_NODE_MAX_SESSIONS valueFrom: configMapKeyRef: name: seleniumhub key: SE_NODE_MAX_SESSIONS - name: SE_NODE_OVERRIDE_MAX_SESSIONS valueFrom: configMapKeyRef: name: seleniumhub key: SE_NODE_OVERRIDE_MAX_SESSIONS - name: SE_SESSION_REQUEST_TIMEOUT value: '900' - name: SE_NODE_GRID_URL valueFrom: configMapKeyRef: name: seleniumhub key: SE_NODE_GRID_URL - name: SE_VNC_NO_PASSWORD valueFrom: configMapKeyRef: name: seleniumhub key: SE_VNC_NO_PASSWORD - name: SE_NODE_SESSION_TIMEOUT valueFrom: configMapKeyRef: name: seleniumhub key: SE_NODE_SESSION_TIMEOUT securityContext: {} ports: - containerPort: 5555 protocol: TCP
Relevant log output
Operating System
Openshift version: 4.11
Docker Selenium version (image tag)
selenium/node-firefox:4.15
Selenium Grid chart version (chart version)
No response
The text was updated successfully, but these errors were encountered: