-
Notifications
You must be signed in to change notification settings - Fork 3.4k
endpoint: Avoid unnecessarily logging a warning during endpoint deletion #40927
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
Conversation
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
Not sure whether v1.18 is affected by this or not to mark for v1.18 backport - I saw this failure condition for the first time today. I just don't know whether we saw it now because we changed something about startup ordering or if it's always been possible and it's just rare enough we don't often see it. |
I'm OK with backporting this as it's just changing the logging for this condition. |
7536c06
to
6d4893c
Compare
It is possible during endpoint restoration for the endpoint to be deleted in the middle of the process. If the endpoint restoration process was waiting for global identities to be synced and the deletion occurs, then the wait for the sync will be canceled. This triggers an unnecessary warning log. To fix, detect that the endpoint is deleted which we can tell by checking if the context was canceled. See cilium#40924 for more details. Fixes: cilium#40924 Signed-off-by: Joe Stringer <joe@cilium.io> Signed-off-by: Chris Tarazi <chris@isovalent.com>
6d4893c
to
d0f8767
Compare
/test Edit: #39370 |
It is possible during endpoint restoration for the endpoint to be
deleted in the middle of the process. If the endpoint restoration
process was waiting for global identities to be synced and the deletion
occurs, then the wait for the sync will be canceled. This triggers an
unnecessary warning log. To fix, detect that the endpoint is deleted
which we can tell by checking if the context was canceled.
See #40924 for more details.
Fixes: #40924
Signed-off-by: Joe Stringer joe@cilium.io
Signed-off-by: Chris Tarazi chris@isovalent.com