Whereabouts leaks IP assignment causing duplicate IPs in OCP 4.18

Solution In Progress - Updated -

Issue

  • In a cluster using the Whereabouts CNI plugin, different pods are assigned the same IP address after a node reboots. This leads to network connectivity issues due to duplicate IPs.

  • For example, two different pods show the same IP address 192.20.131.18 on one of their interfaces:

Pod 1:

$ oc rsh -n ns pod1
sh-4.2$ ip add
...
3: svc-sigk-l: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1800 qdisc noqueue state UP group default qlen 1000
    link/ether XX:XX:XX:96:e8:72 brd ff:ff:ff:ff:ff:ff
    inet 192.20.131.18/24 brd 192.20.131.255 scope global svc-sigk-l
       valid_lft forever preferred_lft forever
...

Pod 2:

$ oc rsh -n ns pod2
sh-4.2$ ip add
...
3: svc-sigk-l: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1800 qdisc noqueue state UP group default qlen 1000
    link/ether XX:XX:XX:dd:d3:09 brd ff:ff:ff:ff:ff:ff
    inet 192.20.131.18/24 brd 192.20.131.255 scope global svc-sigk-l
       valid_lft forever preferred_lft forever
...

Environment

  • Red Hat OpenShift Container Platform 4.18
  • Whereabouts CNI plugin

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content