-
Notifications
You must be signed in to change notification settings - Fork 670
Captured frame from MAC #3591
Comments
I am also seeing a lot of the same error. But the network seems to work ... I am using
PeerDiscovery: enabled
DefaultSubnet: 10.233.64.0/18 My error log looks similar. The more nodes the more errors ... . Very, very annoying ... ERRO: 2019/02/02 23:08:37.833752 Captured frame from MAC (3e:89:96:d5:fb:01) to (ba:18:12:53:40:44) associated with another peer 26:5f:ee:b4:31:b6(mykc-dev-blue-k8s-master-nf-2) |
Same here I'm getting tons of them but network works, only thing I found is that hairpin is off even though kubelet and weave are configured to enable it. |
my yaml setup for the weave pods look like this (created using kubespray)
|
We're both using kubespray and weave 2.5.0 configuration is the same. I'm on k8s 1.12 |
how do you check "veth bridge hairpin is off" ? are you looking into journalctl ? This is how my journalctl log looks like: root@mykc-dev-blue-k8s-master-nf-1:~# journalctl | grep hairpin |
ip -d link show vethwe-bridge
|
Some discussion at #2877 of how this can happen and be innocuous. |
I'm seeing bunch of these error messages. Is it safe to ignore them as I've read somewhere it can be logging issue.
The text was updated successfully, but these errors were encountered: