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

Lens App can not connect to some clusters (RangeError: Maximum call stack size exceeded) #8110

Open
vlasashk opened this issue Oct 17, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@vlasashk
Copy link

vlasashk commented Oct 17, 2024

Describe the bug
Unable to connect to some clusters (in UI keeps loading without any indication of a problem, in logs reports an error)

To Reproduce
Steps to reproduce the behavior:

  1. Open Lens
  2. Click on 'Local Kuberconfigs'
  3. Click cluster to connect to

Expected behavior
Successfully connect to cluster and show cluster info or in case of error show error in UI

Screenshots
exmpl

Environment (please complete the following information):

  • Lens Version: 2024.9.300059-latest
  • OS: MacOS Sonoma 14.4 (23E214)
  • Installation method (e.g. snap or AppImage in Linux): from website

Logs:
When you run the application executable from command line you will see some logging output. Please paste them here:

...
(node:28179) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 11 abort listeners added to [AbortSignal]. MaxListeners is 10. Use events.setMaxListeners() to increase limit
(Use `Lens --trace-warnings ...` to show where the warning was created)
debug:   ┏ [INTERNAL-PROXY]: [JSON-API] request POST https://127.0.0.1:61053/api-kube/apis/authorization.k8s.io/v1/selfsubjectaccessreviews +87ms
...(here configs data)
(node:28179) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 11 abort listeners added to [AbortSignal]. MaxListeners is 10. Use events.setMaxListeners() to increase limit
Error occurred in handler for 'activate-cluster': RangeError: Maximum call stack size exceeded
    at /Applications/Lens.app/Contents/Resources/app.asar/node_modules/@lensapp/cluster-manager-main/dist/index.js:461:19
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /Applications/Lens.app/Contents/Resources/app.asar/node_modules/@lensapp/cluster-manager-main/dist/index.js:485:41
    at async /Applications/Lens.app/Contents/Resources/app.asar/node_modules/@lensapp/cluster-manager-main/dist/index.js:664:35
    at async /Applications/Lens.app/Contents/Resources/app.asar/node_modules/@lensapp/cluster-manager-main/dist/index.js:729:29
    at async _ensure (/Applications/Lens.app/Contents/Resources/app.asar/node_modules/@lensapp/cluster-manager-main/dist/index.js:804:31)
    at async Object.ensure (/Applications/Lens.app/Contents/Resources/app.asar/node_modules/@lensapp/cluster-manager-main/dist/index.js:822:23)
    at async /Applications/Lens.app/Contents/Resources/app.asar/node_modules/@lensapp/cluster-manager-main/dist/index.js:1123:5
    at async WebContents.<anonymous> (node:electron/js2c/browser_init:2:83654)

Kubeconfig:
Quite often the problems are caused by malformed kubeconfig which the application tries to load. Please share your kubeconfig, remember to remove any secret and sensitive information.

your kubeconfig here

Additional context
configs are fine since I'm able to connect to all clusters without any issues via kubectl

@vlasashk vlasashk added the bug Something isn't working label Oct 17, 2024
@clrothmann
Copy link

Thank you for your feedback @vlasashk. To further investigate your issue in more detail, could you please provide the following information: What happens when you manually disconnect and reconnect during this state? -> Right-click on your cluster in the left-hand Navigator, click the corresponding entry in the context menu, and then click on the cluster again. I will pass your issue along with your log excerpts to the corresponding team. Looking forward to your response!

@vlasashk
Copy link
Author

@clrothmann in this state it is not possible to disconnect since the "Disconnect" button is not present
image
Another issue is that if any cluster is in this state is present - the app won't be able to close gracefully and it needs to terminated with SIGKILL

  • normal termination log (no cluster in error state)
    image
  • stuck termination log (with cluster error state)
    image

@NikPoliakov
Copy link

NikPoliakov commented Oct 24, 2024

I am also facing this issue.

Screenshot 2024-10-24 195030

Failed to refresh accessibility: RangeError: Maximum call stack size exceeded

It only happens with one cluster out of 24 I have in Lens.
kubectl and other tools like k9s and Headlamp work just fine.

is there any more information I can provide here ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants