Bug 1700828

Summary:	Sporadic kube-apiserver NLB connection refused response
Product:	OpenShift Container Platform	Reporter:	Stefan Schimanski <sttts>
Component:	Master	Assignee:	Stefan Schimanski <sttts>
Status:	CLOSED ERRATA	QA Contact:	Xingxing Xia <xxia>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.1.0	CC:	aos-bugs, jokerman, mfojtik, mmccomas, yinzhou
Target Milestone:	---
Target Release:	4.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-04 10:47:40 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Stefan Schimanski 2019-04-17 12:54:47 UTC

Description of problem:

In CI we occasionally see connection refused when connecting through the NLB to the kube-apiserver. With /readyz used as NLB target health check and our timing (35 sec kube-apiserver minimum-termination-period, 3*10 sec NLN target unhealthz threshold) this should never happen.

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

4.10

How reproducible:

Randomly in CI.

Additional info:

Comment 5 errata-xmlrpc 2019-06-04 10:47:40 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:0758