You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This looks like a UI messaging issue, although maybe there's something more to it than that.
When using an intercept spec file, you need to have a connection established first before running the intercept file. If the daemon is running but disconnected, you get a decipherable (although somewhat cryptic) message about "rpc" and "No active session". If the daemon is not running, however, the error message is about not being able to reach the cluster.
If the intercept spec file is supposed to be able to run without a connection, then we have a bug and I'm happy to give more information to debug it.
If the intercept spec file is supposed to require a connection, then it'd be nice if the error message in these cases said something about needing to connect before running the intercept file.
I don't see anything in the documentation that specifies whether or not a connection is required, although it's entirely possible that I missed it.
robert@dev-robert:~$ telepresence intercept run ./tp-spec.yaml
Intercept spec "test-spec" started successfully, use ctrl-c to cancel.
robert@dev-robert:~$ telepresence quit
Disconnected
robert@dev-robert:~$ telepresence intercept run ./tp-spec.yaml
telepresence intercept run: error: rpc error: code = Unavailable desc = no active session
See logs for details (2 errors found): "/home/robert/.cache/telepresence/logs/daemon.log"
See logs for details (3 errors found): "/home/robert/.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/telepresenceio/telepresence/issues/new?template=Bug_report.md .
robert@dev-robert:~$ telepresence quit -s
Telepresence Daemons quitting...done
robert@dev-robert:~$ telepresence intercept run ./tp-spec.yaml
Launching Telepresence User Daemon
telepresence intercept run: error: connector.Connect: initial cluster check failed: Get "https://127.0.0.1:6443/version": dial tcp 127.0.0.1:6443: connect: connection refused
Hi @RobertFischer , generally you do need to run telepresence connect before starting an intercept (either global or personal), so that's probably also required with the Intercept Specification. For example, with a global intercept you do need to start by running telepresence connect to your cluster.
Before running your intercept spec, are you able to connect to your cluster and get your pods?
Can you run kubectl get pods to check that?
Perhaps your kubeconfig is not configured such that Telepresence can connect to it.
If that checks out, you could share with us your Intercept Spec for confirmation.
Actually the intercept spec can also take care of your connect, provided it’s properly configured.
This looks like a UI messaging issue, although maybe there's something more to it than that.
When using an intercept spec file, you need to have a connection established first before running the intercept file. If the daemon is running but disconnected, you get a decipherable (although somewhat cryptic) message about "rpc" and "No active session". If the daemon is not running, however, the error message is about not being able to reach the cluster.
If the intercept spec file is supposed to be able to run without a connection, then we have a bug and I'm happy to give more information to debug it.
If the intercept spec file is supposed to require a connection, then it'd be nice if the error message in these cases said something about needing to connect before running the intercept file.
I don't see anything in the documentation that specifies whether or not a connection is required, although it's entirely possible that I missed it.
Logs:
telepresence_logs.zip
Versions:
The text was updated successfully, but these errors were encountered: