Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1438402 - Nope IP is flip flopping between eth0 and eth1 IPs
Nope IP is flip flopping between eth0 and eth1 IPs
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking (Show other bugs)
3.4.0
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Rajat Chopra
Meng Bo
:
Depends On:
Blocks: 1451818 1451828 1451830
  Show dependency treegraph
 
Reported: 2017-04-03 07:09 EDT by Nicolas Nosenzo
Modified: 2017-08-16 15 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: multiple node IP addresses reported in random order by node status Consequence: Sdn controller picks up random one each time Fix: Maintain stickiness of the IP once it is chosen until valid. Result:
Story Points: ---
Clone Of: 1410128
: 1451818 1451828 1451830 (view as bug list)
Environment:
Last Closed: 2017-08-10 01:20:02 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Origin (Github) 13645 None None None 2017-04-10 14:47 EDT
Red Hat Product Errata RHEA-2017:1716 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.6 RPM Release Advisory 2017-08-10 05:02:50 EDT

  None (edit)
Description Nicolas Nosenzo 2017-04-03 07:09:53 EDT
Description of problem:

Each node has 2 NICs (eth0 and eth1), each of them standing on different networks:

eth0 -> 192.168.10.x/24
eth1 -> 10.10.0.x/24

This, caused the nodes to be registered with both IPs on the cluster:

e.g.:

"name": "ocp-node1",

                "addresses": [
                    {
                        "type": "InternalIP",
                        "address": "10.10.0.7"
                    },
                    {
                        "type": "InternalIP",
                        "address": "192.168.10.11"
                    }
                ], 

Randomly, the hostIP is switched between these IPs:



            "host": "node1",
            "hostIP": "192.168.10.7",
            "subnet": "10.130.0.0/23"

            "host": "node2",
            "hostIP": "192.168.10.4",
            "subnet": "10.131.0.0/23"

            "host": "node3",
            "hostIP": "192.168.10.9",
            "subnet": "10.129.0.0/23"

            "host": "node4",
            "hostIP": "10.10.0.7",
            "subnet": "10.128.0.0/23"

            "host": "node5",
            "hostIP": "192.168.10.10",
            "subnet": "10.130.0.0/23"


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

How reproducible:
Almost each time a node is rebooted, it ends up with with a different IP.

Steps to Reproduce:
1. Will add in a comment.
2.
3.

Actual results:
Host IP is switching between eth's IP

Expected results:
Node got registered always with the same Host IP

Additional info:

This bug was originally reported in BZ 1410128, and fixed with errata https://access.redhat.com/errata/RHBA-2017:0218
Comment 2 Rajat Chopra 2017-04-04 17:46:38 EDT
Looks like the master was restarted as well. Unfortunately, if that is true, the master loses all its cache and does not recall what was the previously used address for the node.
Comment 3 Rajat Chopra 2017-04-04 17:47:09 EDT
Could we confirm if the master was restarted as well?
Comment 6 Troy Dawson 2017-04-19 15:34:30 EDT
This has been merged into ocp and is in OCP v3.6.39 or newer.
Comment 8 Meng Bo 2017-04-27 07:36:17 EDT
Recreated the issue by restarting both master vm and node vm with OCP build 3.6.25 on openshift-on-openstack env with multiple NICs.

Cannot reproduce with latest build 3.6.50, after many times tries.

Verify the bug.
Comment 10 errata-xmlrpc 2017-08-10 01:20:02 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:1716

Note You need to log in before you can comment on or make changes to this bug.