Bug 1806330 - [3.11] - ETCD service crash on member when apiservice is started
Summary: [3.11] - ETCD service crash on member when apiservice is started
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-apiserver
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 3.11.z
Assignee: Ryan Phillips
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-23 21:13 UTC by Vladislav Walek
Modified: 2020-02-27 16:46 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-27 16:46:02 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Vladislav Walek 2020-02-23 21:13:05 UTC
Description of problem:

Hello,

we see a lot of timeouts in ETCD when the apiservice is started. The ETCD is healthy and stable, when the api and controller services are down.
However, when we started the api service on one node, the ETCD member immediately went to not healthy status and shows "context deadline exceeded".
Also we see that ETCD starts to change the leader very often.
The whole host is becoming unstable, no ssh commands can be executed, also ping requests are being lost (not rejected).


Version-Release number of selected component (if applicable):
OpenShift Container Platform - atomic-openshift-3.11.88-1.git.0.47f4e98.el7.x86_64

How reproducible:
n/a

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
will attach the logs in private comment


Note You need to log in before you can comment on or make changes to this bug.