I am running OCP 3.7.54. I can only find notes indicating IPv6 is not supported, but no indication in the prereqs that it should be disabled on the nodes. In my case IPv6 is not specifically configured so there are only link local addresses present. I suspect it is causing me problems.
While investigating timeouts during container creation I noticed lots of messages like this: Jul 19 14:00:38 ose-prod-node-09.example.com kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Jul 19 14:00:38 ose-prod-node-09.example.com kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready This is odd because I have no eth0 physical interface, ifcfg-eth0 file, or udev rules referencing it. [root@ose-prod-node-09 ~]# nmcli dev DEVICE TYPE STATE CONNECTION team0 team connected mlag docker0 bridge connected docker0 eno1 ethernet connected team0-eno1 eno2 ethernet connected team0-eno2 eno3 ethernet disconnected -- eno4 ethernet disconnected -- vxlan_sys_4789 vxlan disconnected -- eth0 ethernet unmanaged -- veth00853eea ethernet unmanaged -- ... While looking at the system a couple hours later there was suddenly a second default route added with a lower metric that made the node unreachable. I wonder if this was caused by NetworkManager reacting to a change in the unexplained eth0 interface. Oddly, the default route points to the IP of the tun0 interface as next hop and is directed out this previously nonexistant eth0 interface: [root@ose-prod-node-09 ~]# ip route ls default via 10.1.11.1 dev eth0 <------ ! default via 203.0.113.254 dev team0 proto dhcp metric 350 10.1.0.0/16 dev tun0 scope link 10.1.11.0/24 dev eth0 proto kernel scope link src 10.1.11.196 203.0.113.0/24 dev team0 proto kernel scope link src 203.0.113.9 metric 350 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 172.30.0.0/16 dev tun0 224.0.0.0/4 dev eth0 [root@ose-prod-node-09 ~]# ip -4 -o a 1: lo inet 127.0.0.1/8 scope host lo\ valid_lft forever preferred_lft forever 6: team0 inet 203.0.113.9/24 brd 203.0.113.255 scope global noprefixroute dynamic team0\ valid_lft 70821sec preferred_lft 70821sec 11: docker0 inet 172.17.0.1/16 scope global docker0\ valid_lft forever preferred_lft forever 13: tun0 inet 10.1.11.1/24 brd 10.1.11.255 scope global tun0\ valid_lft forever preferred_lft forever 17845: eth0 inet 10.1.11.196/24 brd 10.1.11.255 scope global eth0\ valid_lft forever preferred_lft forever <---- ! Any idea how or why this eth0 would have been created by NetworkManager? Could it be caused by IPv6 being enabled and triggering all those link state events? _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
