Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1451818 - [3.3] Nope IP is flip flopping between eth0 and eth1 IPs
[3.3] 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.3.0
Unspecified Unspecified
unspecified Severity medium
: ---
: 3.3.1
Assigned To: Ben Bennett
Meng Bo
:
Depends On: 1438402 1451828 1451830
Blocks:
  Show dependency treegraph
 
Reported: 2017-05-17 11:02 EDT by Ben Bennett
Modified: 2017-06-15 14:39 EDT (History)
7 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: No flapping.
Story Points: ---
Clone Of: 1438402
Environment:
Last Closed: 2017-06-15 14:39:42 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
Github openshift/ose/pull/742 None None None 2017-05-17 11:02 EDT
Red Hat Product Errata RHBA-2017:1425 normal SHIPPED_LIVE OpenShift Container Platform 3.5, 3.4, 3.3, and 3.2 bug fix update 2017-06-15 18:35:53 EDT

  None (edit)
Comment 1 Eric Paris 2017-05-31 10:40:25 EDT
https://github.com/openshift/ose/pull/742
Comment 3 Meng Bo 2017-06-05 05:28:13 EDT
Tested on OCP build v3.3.1.33

The node IP will not change during the master and node restarted.
Comment 5 errata-xmlrpc 2017-06-15 14:39:42 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/RHBA-2017:1425

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