-
Notifications
You must be signed in to change notification settings - Fork 24
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
aws-eks-nodeagent container logs errors on startup and shutdown #162
Comments
@rtomadpg just curious, did you notice the comment with:
when you opened this issue? We are trying to improve the experience here with triaging Network Policy agent issues, so I am wondering if you think there is a better way this could have been noticed. |
As for this issue, this is the same as #103. This error log is harmless, and a fix is in progress |
Ouch, so sorry! I checked the new bug flow and indeed that comment is there. Very clearly. |
@jdn5126 maybe a suggestion: when errors are logged by a container named "aws-eks-nodeagent" it's not immediately clear that's related to "Network Policy issues" or "aws-network-policy-agent". Maybe a mention of "aws-eks-nodeagent" in that comment will reduce wrongly filed issues? |
Oh no worries, I was just curious if there was a better setup through GitHub. Good call, I can expand the comment |
Hi everyone, sorry jumpin in on a closed thread. I'm facing the same issue, but without the network policy error mentioned here. Any ideas ? |
@lsabreu96 the error log from this issue is harmless. If you are seeing the |
For anyone reaching this thread because the So not commenting to reopen this issue, just provide information if anyone still running 1.24 lands here! |
What happened:
After upgrading VPC-CNI from
v1.14.1-eksbuild.1
tov1.15.4-eksbuild.1
all theaws-eks-nodeagent
containers logged:And, when I delete a random aws-node pod, I see this:
I believe these errors comes from the
uber-go/zap
dependency, see https://github.com/uber-go/zap/blob/5acd569b6a5264d4c7433cbb278a8336d491715c/logger.go#L398As I am unsure this error is signalling something is (really) wrong and this error was not logged in this project yet, I created the bug.
Attach logs
Let me know if needed.
What you expected to happen:
No errors getting logged.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl version
): v1.27.7-eks-4f4795dcat /etc/os-release
): Amazon Linux 2uname -a
):The text was updated successfully, but these errors were encountered: