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

Browser pods are deleted right after start #60

Open
anusha90267 opened this issue Jul 15, 2024 · 0 comments
Open

Browser pods are deleted right after start #60

anusha90267 opened this issue Jul 15, 2024 · 0 comments

Comments

@anusha90267
Copy link

Hi Team,

We are using Kubernetes 1.27 on our on-premises cluster. We have deployed the application 'Scaling Selenium Tests using Selenoid & Selenosis' on our Kubernetes cluster. In the Selenosis web UI, 'SSE and SELENOID' show as connected. However, when attempting to create sessions, the browser pods are created and then immediately deleted. On the UI sessions page, we see the AJAX error: 502. In the Selenosis pod logs, we encounter the following error:

`

_time="2020-12-21T10:28:20Z" level=error msg="session failed: Post \"http://selenoid-vnc-chrome-87-0-af3177a0-5052-45be-b4e4-9462146e4633.seleniferous:4445/wd/hub/session\": dial tcp: lookup selenoid-vnc-chrome-87-0-af3177a0-5052-45be-b4e4-9462146e4633.seleniferous on 10.96.0.10:53: no such host" request="POST /wd/hub/session" request_id=fa150040-86c1-4224-9e5c-21416b1d9f5c time_elapsed=5.73s_

`

We have followed the steps provided in the description to modify the CoreDNS pod configmap, but the issue persists. Please let us know if there are any other solutions or troubleshooting steps we should follow. We have been facing this issue for multiple days, and your inputs would be very helpful.

Thank you.

``

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant