Skip to content
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]: [Grid] Custom node stereotypes are missing in session capabilities #14316

Closed
VietND96 opened this issue Jul 29, 2024 · 2 comments · Fixed by #14323
Closed

[🐛 Bug]: [Grid] Custom node stereotypes are missing in session capabilities #14316

VietND96 opened this issue Jul 29, 2024 · 2 comments · Fixed by #14323

Comments

@VietND96
Copy link
Member

VietND96 commented Jul 29, 2024

What happened?

The issue is found after docker-selenium tried to add SeleniumHQ/docker-selenium#2323

Session capabilities running in node Chrome and Edge are missing custom node stereotypes. Meanwhile, node Firefox is fine. See below screenshots

Node stereotypes added "se:containerName":"my-chrome-name-rr6s5-86shd"
image

When looking into session capabilities running in this node, could not see se:containerName
image

Did the same for node Firefox, we could see se:containerName in session capabilities
image

When compare session caps between node Chrome and Firefox, it looks like
image

How can we reproduce the issue?

docker-selenium starts Node with

environment:
  - SE_NODE_CONTAINER_NAME: this_specific_node_is_use

client binding run tests

ChromeOptions options = new ChromeOptions();
WebDriver driver = new RemoteWebDriver(new URL("http://localhost:4444"), options);
driver.get("https://selenium.dev");
driver.quit();

Relevant log output

[[node.driver-configuration]]
display-name = "chrome"
stereotype = '{"browserName": "chrome", "browserVersion": "126.0", "platformName": "Linux", "goog:chromeOptions": {"binary": "/usr/bin/chromium"}, "se:containerName": "my-chrome-name-b4d69f744-wrg4c"}'
max-sessions = 1
    
Starting Selenium Grid Node...
2024-07-29T02:21:48Asia [Probe.Startup] - Wait for the Node to report its status
2024-07-29T02:21:53Asia [Probe.Startup] - Wait for the Node to report its status
09:21:53.678 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
09:21:53.685 INFO [OpenTelemetryTracer.createTracer] - Using OpenTelemetry for tracing
09:21:56.377 INFO [UnboundZmqEventBus.<init>] - Connecting to tcp://selenium-hub.selenium:4442 and tcp://selenium-hub.selenium:4443
09:21:56.876 INFO [UnboundZmqEventBus.<init>] - Sockets created
09:21:57.878 INFO [UnboundZmqEventBus.<init>] - Event bus ready
2024-07-29T02:21:58Asia [Probe.Startup] - Wait for the Node to report its status
09:21:58.781 INFO [NodeServer.createHandlers] - Reporting self as: http://10.244.147.135:6666
09:21:58.886 INFO [NodeOptions.getSessionFactories] - Detected 1 available processors
09:21:59.283 INFO [NodeOptions.report] - Adding chrome for {"browserName": "chrome","browserVersion": "126.0","goog:chromeOptions": {"binary": "\u002fusr\u002fbin\u002fchromium"},"platformName": "linux","se:containerName": "my-chrome-name-b4d69f744-wrg4c","se:downloadsEnabled": true,"se:noVncPort": 7900,"se:vncEnabled": true} 1 times
09:21:59.386 INFO [Node.<init>] - Binding additional locator mechanisms: relative
09:22:00.676 INFO [NodeServer$1.start] - Starting registration process for Node http://10.244.147.135:6666
09:22:00.677 INFO [NodeServer.execute] - Started Selenium node 4.23.0 (revision 77010cd): http://10.244.147.135:6666
09:22:00.776 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
09:22:02.580 INFO [NodeServer.lambda$createHandlers$2] - Node has been added
...

09:27:42.088 INFO [LocalNode.newSession] - Session created by the Node. Id: 56fbb62b30d467cfdedf9d887c28766d, Caps: Capabilities {acceptInsecureCerts: false, browserName: chrome, browserVersion: 126.0.6478.182, chrome: {chromedriverVersion: 126.0.6478.182 (5b5d8292ddf..., userDataDir: /tmp/.org.chromium.Chromium...}, fedcm:accounts: true, goog:chromeOptions: {debuggerAddress: localhost:42235}, networkConnectionEnabled: false, pageLoadStrategy: normal, platformName: linux, proxy: Proxy(), se:bidiEnabled: false, se:cdp: wss://10.1.0.93/selenium/se..., se:cdpVersion: 126.0.6478.182, se:downloadsEnabled: true, se:name: test_download_file (ChromeT..., se:recordVideo: true, se:screenResolution: 1920x1080, se:vnc: wss://10.1.0.93/selenium/se..., se:vncEnabled: true, se:vncLocalAddress: ws://10.244.147.135:7900, setWindowRect: true, strictFileInteractability: false, timeouts: {implicit: 0, pageLoad: 300000, script: 30000}, unhandledPromptBehavior: dismiss and notify, webauthn:extension:credBlob: true, webauthn:extension:largeBlob: true, webauthn:extension:minPinLength: true, webauthn:extension:prf: true, webauthn:virtualAuthenticators: true}

Operating System

docker-selenium

Selenium version

4.23.0

What are the browser(s) and version(s) where you see this issue?

Chrome, Edge

What are the browser driver(s) and version(s) where you see this issue?

v127.0

Are you using Selenium Grid?

4.23.0

Copy link

@VietND96, 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.

Thank you!

Copy link

github-actions bot commented Sep 8, 2024

This issue has been automatically locked since there has not been any recent activity since it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked and limited conversation to collaborators Sep 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant