Open tamis-laan opened 2 weeks ago
@tamis-laan, 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!
When helm install (upgrade) successfully, a note displays with the Hub URL that can be accessed from outside. What is it? Also, may I know if these values worked with the previous chart version?
@VietND96
"docker-selenium" already exists with the same configuration, skipping
pod/etcd-minikube condition met
pod/kube-apiserver-minikube condition met
pod/kube-controller-manager-minikube condition met
pod/kube-scheduler-minikube condition met
pod/storage-provisioner condition met
Release "selenium-grid" does not exist. Installing it now.
NAME: selenium-grid
LAST DEPLOYED: Sat Jun 22 20:17:29 2024
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
Selenium Grid Server deployed successfully.
export POD_NAME=$(kubectl get pods -n default -l "app.kubernetes.io/name=selenium-grid-selenium-hub,app.kubernetes.io/instance=selenium-grid" -o jsonpath="{.items[0].metadata.name}")
echo "Point your WebDriver tests to http://localhost:4444/wd/hub"
kubectl -n default port-forward $POD_NAME 4444:4444
2. Within Kubernetes cluster, you can use following Service endpoint:
http://selenium-grid-selenium-hub.default.svc:4444
I changed the url to:
driver = webdriver.Remote(
# command_executor="http://selenium-grid-selenium-hub.default.svc.cluster.local:4444/wd/hub",
command_executor="http://selenium-grid-selenium-hub.default.svc:4444",
options=chrome_options
)
I also tried http://selenium-grid-selenium-hub.default.svc:4444/wd/hub
but in both cases same error.
BTW nothing is logged by the hub deployment when trying to connect.
When you running the script on host, I don't think host could reach the DNS selenium-grid-selenium-hub.default.svc
Try to following steps to expose Hub to host port 4444
export POD_NAME=$(kubectl get pods -n default -l "app.kubernetes.io/name=selenium-grid-selenium-hub,app.kubernetes.io/instance=selenium-grid" -o jsonpath="{.items[0].metadata.name}")
kubectl -n default port-forward $POD_NAME 4444:4444
Then point your WebDriver tests to http://localhost:4444/wd/hub
@VietND96 I'm stupid but not that stupid ;-)
No I'm running the script as a kubernetes deployment in the same default namespace. I also tested it using a port forward as you described and I get the same error message.
I am not sure how the service type LoadBalancer works in Minikube. I would suggest another config that you can try
hub:
serviceType: NodePort
And in script connect to http://localhost:31444/wd/hub
What happened?
I'm trying to run the selenium helm chart and connecting using python:
But I get the following error:
The error message non descriptive as the it's empty.
Command used to start Selenium Grid with Docker (or Kubernetes)
Relevant log output
Operating System
Minikube
Docker Selenium version (image tag)
4.22.0
Selenium Grid chart version (chart version)
No response