selenium: Selenium Hub does not update Node's configuration if started after the node
Selenium Version:
3.12.0
Browser:
Any
Expected Behavior -
Node configuration is updated with corresponding Hub parameters
Actual Behavior -
Configuration for the node is not updated with Hub parameters
Config for the hub :
browserTimeout : 240
debug : true
help : false
jettyMaxThreads : -1
port : 4444
role : hub
timeout : 15
enablePassThrough : false
cleanUpCycle : 5000
host : 10.64.214.26
maxSession : 5
hubConfig : /opt/selenium/config.json
capabilityMatcher : org.openqa.grid.internal.utils.DefaultCapabilityMatcher
newSessionWaitTimeout : -1
throwOnCapabilityNotPresent : true
registry : org.openqa.grid.internal.DefaultGridRegistry
Config details :
hub launched with : -browserTimeout 240 -debug true -help false -jettyMaxThreads -1 -port 4444 -role hub -timeout 15 -enablePassThrough false -cleanUpCycle 5000 -host 10.64.214.26 -maxSession 5 -hubConfig /opt/selenium/config.json -capabilityMatcher org.openqa.grid.internal.utils.DefaultCapabilityMatcher -newSessionWaitTimeout -1 -throwOnCapabilityNotPresent true -registry org.openqa.grid.internal.DefaultGridRegistry
the final configuration comes from :
the default :
browserTimeout : 0
debug : false
help : false
port : 4444
role : hub
timeout : 1800
enablePassThrough : true
cleanUpCycle : 5000
capabilityMatcher : org.openqa.grid.internal.utils.DefaultCapabilityMatcher
newSessionWaitTimeout : -1
throwOnCapabilityNotPresent : true
registry : org.openqa.grid.internal.DefaultGridRegistry
updated with params :
browserTimeout : 240
debug : false
help : false
jettyMaxThreads : -1
port : 4444
role : hub
timeout : 15
enablePassThrough : true
cleanUpCycle : 5000
maxSession : 5
capabilityMatcher : org.openqa.grid.internal.utils.DefaultCapabilityMatcher
newSessionWaitTimeout : -1
throwOnCapabilityNotPresent : true
registry : org.openqa.grid.internal.DefaultGridRegistry
Steps to reproduce -
- Start a node with default parameters, check that it cannot register to the hub
- Start a hub with environment GRID_TIMEOUT=15
- Check node configuration after the registration on the hub
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 17 (6 by maintainers)
Well, after I comment on this post, I tried to add timeout parameters to nodes with SE_OPTS, and it works!
https://gist.github.com/derinbay/ebe8192891950f7edc355de5b8e16030
I’m not sure we’ll be able to fix it in 3.13, I target to 3.14.
@Niceplace When grid hub is starting first, then nodes are creating and connects to grid hub, this problem ocurs. For a workaround, first create the nodes, then create the grid hub. It respects the timeout values like this.
Edit: I just saw that you already did with that order. In my case it’s working.
@barancev I hope this will fix soon.