Open varsha-rav opened 3 months ago
@varsha-rav, thank you for creating this issue. We will troubleshoot it as soon as we can.
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.
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.
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)
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