Bug 1753443 - e2e-azure: TLS handshake error
Summary: e2e-azure: TLS handshake error
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-apiserver
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.3.0
Assignee: Stefan Schimanski
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-19 00:18 UTC by Kirsten Garrison
Modified: 2020-02-27 23:48 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-30 10:53:28 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Kirsten Garrison 2019-09-19 00:18:12 UTC 
Description of problem:
In Azure e2e runs we are seeing consistently TLS errors coming from kube-apiserver

How reproducible:
See relevant runs (both passing and failing) https://testgrid.k8s.io/redhat-openshift-release-informing#redhat-canary-openshift-ocp-installer-e2e-azure-4.2

Actual results:
kube-apiserver logs have consistent errors: 
"TLS handshake error from 168.63.129.16:63025: EOF" 

for example run see: https://storage.googleapis.com/origin-ci-test/logs/canary-openshift-ocp-installer-e2e-azure-4.2/305/artifacts/e2e-azure/pods/openshift-kube-apiserver_kube-apiserver-ci-op-kw7pw2rj-282fe-frgtd-master-0_kube-apiserver-6.log

This error is also affecting/filtering to the machine-config-server and flooding those logs: 
https://storage.googleapis.com/origin-ci-test/logs/canary-openshift-ocp-installer-e2e-azure-4.2/305/artifacts/e2e-azure/pods/openshift-machine-config-operator_machine-config-server-6fqw6_machine-config-server.log


Expected results:
No TLS handshake errors in kube-apiserver
Note You need to log in before you can comment on or make changes to this bug.