Bug 1883903

Summary:	SDN's kube-rbac-proxy may fail becuase the kube-proxy is not ready
Product:	OpenShift Container Platform	Reporter:	Juan Luis de Sousa-Valadas <jdesousa>
Component:	Networking	Assignee:	Juan Luis de Sousa-Valadas <jdesousa>
Networking sub component:	openshift-sdn	QA Contact:	zhaozhanqi <zzhao>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	low
Priority:	medium	CC:	weliang
Version:	4.6
Target Milestone:	---
Target Release:	4.6.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:	2020-10-27 16:47:06 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:

Description Juan Luis de Sousa-Valadas 2020-09-30 13:38:07 UTC

Description of problem:
When starting a cluster we can see the kube-rbac-proxy failing because it's unable to reach kubernetes.default.svc.

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

How reproducible:
Intermittent

Steps to Reproduce:
1. Create a new cluster
2. Look for restarts of SDN pods on openshift-sdn namespace


Actual results:
Sometimes the service is not available yet causing some restarts

Expected results:
We should retry for a while before failing.


Additional info:

Comment 2 Weibin Liang 2020-10-01 18:28:25 UTC

After installing several new clusters, does not see any Traceback for kube-proxy.

Talked with @valadas, it's very difficult to reproduce this bug.

QE verify this bug now and will re open it if we see the same issue in the future.

Comment 5 errata-xmlrpc 2020-10-27 16:47: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 (OpenShift Container Platform 4.6 GA Images), 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-2020:4196