azure-container-networking
azure-container-networking copied to clipboard
Telemetry leaks sockets on error
What happened: Starting telemetry gives error
2024/04/20 00:17:26 [9756] StartServer: unmarshal error:invalid character 'm' looking for beginning of value
2024/04/24 16:39:41 [9756] StartServer: unmarshal error:invalid character ':' after top-level value
2024/04/24 16:39:42 [9756] StartServer: unmarshal error:invalid character ':' looking for beginning of value
and does not clean up/close connections on error.
What you expected to happen:
The unmarshal error should not occur and the connections should be closed properly on error.
How to reproduce it:
Start an AKS cluster and create a pod.
Orchestrator and Version (e.g. Kubernetes, Docker):
Operating System (Linux/Windows):
Kernel (e.g. uanme -a for Linux or $(Get-ItemProperty -Path "C:\windows\system32\hal.dll").VersionInfo.FileVersion for Windows):
Anything else we need to know?: [Miscellaneous information that will assist in solving the issue.]