Bug 1410128 – [3.4] http traffic failures when accessing pod from outside of the cluster

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1410128 - [3.4] http traffic failures when accessing pod from outside of the cluster

Summary:	[3.4] http traffic failures when accessing pod from outside of the cluster

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Networking (Show other bugs)
Sub Component:
Version:	3.3.1
Hardware:	Unspecified Unspecified

Priority	urgent Severity urgent
Target Milestone:	---
Target Release:	3.4.z
Assigned To:	Ben Bennett
QA Contact:	Meng Bo
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	1400609
Blocks:
	Show dependency tree / graph

Reported:	2017-01-04 09:28 EST by Scott Dodson
Modified:	2017-01-31 15:19 EST (History)
CC List:	11 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	Cause: The IP addresses for a node were not sorted. Consequence: When the first is chosen, it may be different from the last one used, so the IP address would appear to have changed. OpenShift would update the node -> IP mapping and that causes problems with everything moving from one interface to another. Fix: Sort the addresses. Result: The traffic flows correctly and the addresses don't change.
Story Points:	---
Clone Of:	1400609
Clones:	1438402 (view as bug list)
Environment:
Last Closed:	2017-01-31 15:19:25 EST
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)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Github	openshift/ose/pull/529	None	None	None	2017-01-05 09:42 EST
Red Hat Product Errata	RHBA-2017:0218	normal	SHIPPED_LIVE	Red Hat OpenShift Container Platform 3.4.1.2 bug fix update	2017-01-31 20:18:20 EST

Groups: None (edit)

Comment 3 Meng Bo 2017-01-22 04:49:11 EST

Tested with OCP build 3.4.1.0

Issue has been fixed.
No IP flip-flop in master log, and the route can be accessed without 503.

Comment 5 errata-xmlrpc 2017-01-31 15:19:25 EST

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:0218

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