Bug 2079832

Description of problem:

nodeip-configuration and ovs-configure select different primary IP addresses

Even thought OVN stably selects an interface on UPI the cluster fails.  OVN is not communicating with kubelet.

OVN is not abiding by https://docs.openshift.com/container-platform/4.10/support/troubleshooting/troubleshooting-network-issues.html#nw-how-nw-iface-selected_troubleshooting-network-issues

OVN's "correct" interface is not matching /etc/systemd/system/kubelet.service.d/20-nodenet.conf

> For installations on bare metal or with virtual machines that have more than one network interface controller (NIC), the NIC that OpenShift Container Platform uses for communication with the Kubernetes API server is determined by the nodeip-configuration.service service unit that is run by systemd when the node boots. The service iterates through the network interfaces on the node and the first network interface that is configured with a subnet than can host the IP address for the API server is selected for OpenShift Container Platform communication.


configure-ovs needs to:

> Create a shell script that determines the IP address to use for OpenShift Container Platform communication. Have the script create a custom unit file such as /etc/systemd/system/kubelet.service.d/98-nodenet-override.conf. Use the custom unit file, 98-nodenet-override.conf, to set the KUBELET_NODE_IP environment variable to the IP address.


Or vice-versa if KUBELET_NODE_IP is defined then that is the "correct" IP and configure-ovs should use that instead of the default route logic.

/etc/systemd/system/kubelet.service.d/20-nodenet.conf
[Service]
Environment="KUBELET_NODE_IP=10.123.74.75" "KUBELET_NODE_IPS=10.123.74.75"


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: