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

Initial cluster check failure could be more helpful #3182

Open
dsyer opened this issue May 15, 2023 · 3 comments
Open

Initial cluster check failure could be more helpful #3182

dsyer opened this issue May 15, 2023 · 3 comments
Labels
feature New feature or enhancement request

Comments

@dsyer
Copy link

dsyer commented May 15, 2023

$ telepresence list
telepresence: error: connector.Connect: initial cluster check failed: Get "https://dsyer-tap-demo-mskfvjde.hcp.eastus.azmk8s.io:443/version": dial tcp: lookup dsyer-tap-demo-mskfvjde.hcp.eay

See logs for details (2 errors found): "/home/dsyer/.cache/telepresence/logs/daemon.log"

See logs for details (3 errors found): "/home/dsyer/.cache/telepresence/logs/connector.log"
If you think you have encountered a bug, please run `telepresence gather-logs` and attach the telepresence_logs.zip to your github issue or create a new one: https://github.com/telepresence.

The cluster is no longer accessible (it was destroyed on AKS by a reaper agent that I don't control), so I understand the problem, but

a) the error isn't very helpful - it could just tell me in plain language that the current cluster isn't accessible
b) the only way I know to fix it is to manually delete the ~/.cache/telepresence (if that's the right thing to do maybe telepresence should tell me so, or offer to do it for me)

@cindymullins-dw cindymullins-dw added the feature New feature or enhancement request label May 15, 2023
@thallgren
Copy link
Member

@dsyer why is this fixed by removing the cache? AFAIK, telepresence will try and access the same cluster regardless because it uses your kubeconfig, and the kubeconfig is not in the cache.

@dsyer
Copy link
Author

dsyer commented Jun 11, 2023

I forget. I think maybe when the cache was removed I got a more sensible error message. I was able to debug and make progress anyway.

Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment, or this will be closed in 7 days.

@github-actions github-actions bot added the stale Issue is stale and will be closed label Aug 16, 2024
@thallgren thallgren removed the stale Issue is stale and will be closed label Aug 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or enhancement request
Projects
None yet
Development

No branches or pull requests

3 participants