Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1781678

Summary: 17 min frozen leader election due to TCP networking issues, was: kube-apiserver Progressing=True: 1 nodes are at revision 4; 2 nodes are at revision 6
Product: OpenShift Container Platform Reporter: Stefan Schimanski <sttts>
Component: kube-apiserverAssignee: Stefan Schimanski <sttts>
Status: CLOSED ERRATA QA Contact: xiyuan
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.3.0CC: aos-bugs, hekumar, mfojtik, nagrawal, sttts, wking, xxia
Target Milestone: ---   
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1779796 Environment:
Last Closed: 2020-01-23 11:18:20 UTC Type: ---
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: 1779796    
Bug Blocks:    

Comment 6 xiyuan 2019-12-23 10:29:05 UTC
Didn't see many of "key failed with : clusteroperator/kube-apiserver is not Available" in  https://search.svc.ci.openshift.org/?search=clusteroperator%2Fkube-apiserver+is+not+Available&maxAge=336h&context=2&type=all.
It reported twice at most shown as: https://storage.googleapis.com/origin-ci-test/logs/periodic-ci-openshift-knative-eventing-release-v0.6.0-e2e-aws/178/build-log.txt.
Verification pass.

Comment 8 errata-xmlrpc 2020-01-23 11:18:20 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-2020:0062