Cluster Bootstrap Fails Due to etcd Errors

Solution Verified - Updated -

Issue

Cluster bootstrap fails due to etcd errors such as:

2019-07-22T15:37:56.938597970+00:00 stderr F I0722 15:37:56.938540       1 run.go:134] checking against etcd-2.
2019-07-22T15:38:01.939742071+00:00 stderr F E0722 15:38:01.939700       1 run.go:63] error looking up self: could not resolve member "etcd-2."

Similar errors might be seen in the bootkube.sh output.

Jul 17 15:57:09 system1 bootkube.sh[11913]: https://etcd-1.apps.x86.domain.fake:2379 is unhealthy: failed to commit proposal: context deadline exceeded
Jul 17 15:57:09 system1 bootkube.sh[11913]: https://etcd-0.apps.x86.domain.fake:2379 is unhealthy: failed to commit proposal: context deadline exceeded
Jul 17 15:57:09 system1 bootkube.sh[11913]: Error: unhealthy cluster

Environment

  • Red Hat OpenShift Container Platform v4.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content