Bug 1737683 - openshift-apiserver pod fall into CrashLoopBackOff when proxy enabled
Summary: openshift-apiserver pod fall into CrashLoopBackOff when proxy enabled
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: openshift-apiserver
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2.0
Assignee: Stefan Schimanski
QA Contact: Gaoyun Pei
URL:
Whiteboard:
Depends On: 1740027
Blocks: 1734314
TreeView+ depends on / blocked
 
Reported: 2019-08-06 04:56 UTC by Gaoyun Pei
Modified: 2019-10-16 06:35 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:34:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-kube-apiserver-operator pull 550 0 'None' closed Bug 1737683: Sort the EnvVar from Proxy string map 2020-10-07 03:17:59 UTC
Github openshift cluster-openshift-apiserver-operator pull 220 0 'None' closed Bug 1737683: bump (*) to observe Proxy status instead of spec 2020-10-07 03:18:08 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:35:05 UTC

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
Note You need to log in before you can comment on or make changes to this bug.