Bug 1768436

Summary:	[4.2] backport kube-proxy fix for spurious connection resets
Product:	OpenShift Container Platform	Reporter:	Dan Winship <danw>
Component:	Networking	Assignee:	Dan Winship <danw>
Networking sub component:	openshift-sdn	QA Contact:	zhaozhanqi <zzhao>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	zzhao
Version:	4.2.0
Target Milestone:	---
Target Release:	4.2.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1762298	Environment:
Last Closed:	2019-12-11 22:36:06 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1762298
Bug Blocks:

Comment 2 zhaozhanqi 2019-12-02 06:49:23 UTC

Verified this bug on 4.2.0-0.ci-2019-11-30-132200

sh-4.2# iptables-save | grep INVALID | grep KUBE-FOR
-A KUBE-FORWARD -m conntrack --ctstate INVALID -j DROP

Comment 4 errata-xmlrpc 2019-12-11 22:36:06 UTC

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-2019:4093