search

telepresenceio / telepresence

Local development against a remote Kubernetes or OpenShift cluster
https://www.telepresence.io
Other
6.53k stars 513 forks source link

ReportMetrics failed errors #3604

Closed lkoniecz closed 4 months ago

lkoniecz commented 4 months ago

[Uploading telepresence_logs.zip…]() Describe the bug We are seeing these logs in every traffic agent installed on the cluster

2024-05-31 07:26:35.5671 debug   sidecar/handleIntercept : Accept got connection from 127.0.0.1:56848 : lis=":0"
2024-05-31 07:26:35.5671 debug   sidecar/handleIntercept : Creating tunnel to client 5059d3bd-436f-4d41-acc4-9c1859d82497 for id tcp 127.0.0.1:56848 -> 127.0.0.1:1036 : lis=":0"
2024-05-31 07:26:35.5672 debug   sidecar/handleIntercept : Unable to create tunnel to client 5059d3bd-436f-4d41-acc4-9c1859d82497 for id tcp 127.0.0.1:56848 -> 127.0.0.1:1036: no dial watcher : lis=":0"
2024-05-31 07:26:35.5672 debug   sidecar/handleIntercept : creating tunnel to manager for id tcp 127.0.0.1:56848 -> 127.0.0.1:1036 : lis=":0"
2024-05-31 07:26:35.8993 debug   sidecar/handleIntercept : Done serving connection from 127.0.0.1:56848 : lis=":0"
2024-05-31 07:26:35.9003 error   sidecar/handleIntercept : ReportMetrics failed: rpc error: code = Unimplemented desc = unknown method ReportMetrics for service telepresence.manager.Manager : lis=":0"
2024-05-31 07:26:50.5674 debug   sidecar/handleIntercept : Accept got connection from 127.0.0.1:47504 : lis=":0"
2024-05-31 07:26:50.5674 debug   sidecar/handleIntercept : Creating tunnel to client 5059d3bd-436f-4d41-acc4-9c1859d82497 for id tcp 127.0.0.1:47504 -> 127.0.0.1:1036 : lis=":0"
2024-05-31 07:26:50.5675 debug   sidecar/handleIntercept : Unable to create tunnel to client 5059d3bd-436f-4d41-acc4-9c1859d82497 for id tcp 127.0.0.1:47504 -> 127.0.0.1:1036: no dial watcher : lis=":0"

To Reproduce Steps to reproduce the behavior:

  1. telepresence connect --namespace my-ns
  2. telepresence intercept java-server-mobile --workload java-server --port 1035:1035 --mechanism=tcp
  3. telepresence intercept java-server-native --workload java-server --port 1036:1036 --mechanism=tcp

Expected behavior I would like to understand what do these logs mean

Versions (please complete the following information):

thallgren commented 4 months ago

Thr traffic-manager is old enough to lack support for metrics reporting. The error should otherwise affect the functionality.

Please upgrade to get rid of the log statements.

lkoniecz commented 4 months ago

I am afraid I don't understand. Are you referring to the minor version mismatch between the client and the server? Will it stop reporting the error If I downgrade the client to 2.14?