Bug 1737683

Summary:	openshift-apiserver pod fall into CrashLoopBackOff when proxy enabled
Product:	OpenShift Container Platform	Reporter:	Gaoyun Pei <gpei>
Component:	openshift-apiserver	Assignee:	Stefan Schimanski <sttts>
Status:	CLOSED ERRATA	QA Contact:	Gaoyun Pei <gpei>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.2.0	CC:	aos-bugs, mfojtik, slaznick, wzheng
Target Milestone:	---	Keywords:	TestBlocker
Target Release:	4.2.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-10-16 06:34:48 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:
Embargoed:
Bug Depends On:	1740027
Bug Blocks:	1734314

Comment 1 Standa Laznicka 2019-08-07 12:24:42 UTC

Your noProxy configuration does not seem to include the cluster defaults which you'll need to do until https://github.com/openshift/cluster-network-operator/pull/245 is merged and https://bugzilla.redhat.com/show_bug.cgi?id=1738284 is closed.

Comment 2 Standa Laznicka 2019-08-09 07:53:50 UTC

Removing the dependency so that CI allows to push both PRs in parallel

Comment 6 Standa Laznicka 2019-08-15 07:07:25 UTC

The linked PRs all merged, moving to MODIFIED.

Comment 8 Gaoyun Pei 2019-08-16 04:31:55 UTC

Verify this bug with 4.2.0-0.nightly-2019-08-15-205330

kube-apiserver and openshift-apiserver pods are running well.

Comment 9 errata-xmlrpc 2019-10-16 06:34:48 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:2922