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
Describe the bug
When proxy process gets killed by OOM, there's no chance for the proxy to close them obviously. However, NSM might not be able to clean them up either when the MaxTokenLifetime expires due to rpc error: code = PermissionDenied desc = no sufficient privileges.
The old interfaces do not seem to cause any problem, but they are confusing. (Their IPs are also leaked.)
The connected peer interface in LB also remains. (and can be used to reach the proxy).
To Reproduce
Steps to reproduce the behavior:
Kill a proxy process using KILL signal. (For example from its worker.)
Wait the container to recover and check the NSM interfaces towards LBs.
Wait MaxTokenLifetime (10 minutes by default) and check the interfaces agains. If they are present check the logs of the local nsmgr or forwarder for the Close.
Expected behavior
The interfaces should be event removed (probably by NSM).
(Resolving the leaked IP issue sound much more complex.)
There were improvements in NSM related to cleaning up connections. Haven't noticed "PersmissionDenied" error for a while.
There were also improvements in Meridio:
-IP garbage collection for Meridio IPAM: #527
-Proxy can restore previous connections to LBs by learning them from NSMgr using NSM's Monitor Connection feature: #536 #542
Run verification tests with most recent Meridio and NSM >= v.1.13.2
Describe the bug
When proxy process gets killed by OOM, there's no chance for the proxy to close them obviously. However, NSM might not be able to clean them up either when the MaxTokenLifetime expires due to
rpc error: code = PermissionDenied desc = no sufficient privileges
.The old interfaces do not seem to cause any problem, but they are confusing. (Their IPs are also leaked.)
The connected peer interface in LB also remains. (and can be used to reach the proxy).
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The interfaces should be event removed (probably by NSM).
(Resolving the leaked IP issue sound much more complex.)
Context
Network Service Mesh: v1.6.2
Meridio: 115ca87
Author: Lionel Jouin lionel.jouin@est.tech
Date: Fri Mar 24 19:25:56 2023 +0100
Use Helm chart to deploy e2e operator env
Logs
The text was updated successfully, but these errors were encountered: