cilium: Found two node IDs for the same node errors

Is there an existing issue for this?

• I have searched the existing issues

What happened?

1. restarted cilium-agent daemonsets in multiple clusters
2. agents in multiple clusters all complain about Found two node IDs for various nodeName but different node IDs

Seems it may just be nodes being deleted from clusters, not just agents restarting.

Cilium Version

Daemon: 1.12.8 87d8561 2023-03-15T19:28:16+01:00 go version go1.18.10 linux/amd64

Kernel Version

Linux ip-10-206-123-81 5.15.0-1030-aws #34~20.04.1-Ubuntu SMP Tue Jan 24 15:16:46 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Kubernetes Version

Server Version: version.Info{Major:"1", Minor:"22+", GitVersion:"v1.22.16-eks-ffeb93d", GitCommit:"52e500d139bdef42fbc4540c357f0565c7867a81", GitTreeState:"clean", BuildDate:"2022-11-29T18:41:42Z", GoVersion:"go1.16.15", Compiler:"gc", Platform:"linux/amd64"}

Sysdump

No response

Relevant log output

`level=error msg="Found two node IDs (0 and 4176) for the same node" ipAddr=10.199.160.233 nodeName=ip-10-199-150-180.ec2.internal subsys=linux-datapath`

Anything else?

Spot checking, it seems the nodeName being logged are for non-existent nodes so far

Code of Conduct

• I agree to follow this project’s Code of Conduct