Hello All,
I’m running rancher 2.5.8 on docker 20.10.2 on Ubuntu LTS 20.04.2.
Logs are flooded with:
Jul 09 09:40:30 rancher kernel: cni0: port 1(veth862a1ae7) entered disabled state
Jul 09 09:40:30 rancher kernel: device veth862a1ae7 left promiscuous mode
Jul 09 09:40:30 rancher kernel: cni0: port 1(veth862a1ae7) entered disabled state
Jul 09 09:40:30 rancher kernel: cni0: port 2(veth38803376) entered disabled state
Jul 09 09:40:30 rancher kernel: device veth38803376 left promiscuous mode
Jul 09 09:40:30 rancher kernel: cni0: port 2(veth38803376) entered disabled state
Jul 09 09:40:31 rancher kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Jul 09 09:40:31 rancher kernel: cni0: port 1(vethbff5296c) entered blocking state
Jul 09 09:40:31 rancher kernel: cni0: port 1(vethbff5296c) entered disabled state
Jul 09 09:40:31 rancher kernel: device vethbff5296c entered promiscuous mode
Jul 09 09:40:31 rancher kernel: cni0: port 1(vethbff5296c) entered blocking state
Jul 09 09:40:31 rancher kernel: cni0: port 1(vethbff5296c) entered forwarding state
Jul 09 09:40:31 rancher kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Jul 09 09:40:31 rancher kernel: cni0: port 2(vethf8c533ea) entered blocking state
Jul 09 09:40:31 rancher kernel: cni0: port 2(vethf8c533ea) entered disabled state
Jul 09 09:40:31 rancher kernel: device vethf8c533ea entered promiscuous mode
Jul 09 09:40:31 rancher kernel: cni0: port 2(vethf8c533ea) entered blocking state
Jul 09 09:40:31 rancher kernel: cni0: port 2(vethf8c533ea) entered forwarding state
bad enough that the local root drive is filling.
An online search shows somewhat similar issues but with pods on the K8S cluster also unable to connect to the API. Rancher and the K8S cluster appear seem to be working fine.
Grateful for any help…
Randy in Seattle