search
Ctrlk

Master Node Fails to Converge with Error "client: etcd cluster is unavailable or misconfigured

hashtag
Problem

BareOS Platform9 Managed Kubernetes Cluster failed to converge with the following errors observed on one of the Master Node.

Error:  client: etcd cluster is unavailable or misconfigurederror #0: client: endpoint http://127.0.0.1:2379 exceeded header timeouterror #1: client: endpoint http://127.0.0.1:4001 exceeded header timeout
rafthttp: failed to dial fced1bcbbd9545a2 on stream Message (dial tcp 10.25.41.82:2380: getsockopt: no route to host)rafthttp: failed to dial fced1bcbbd9545a2 on stream MsgApp v2 (dial tcp 10.25.41.82:2380: getsockopt: no route to host)

hashtag
Environment

  • Platform9 Managed Kubernetes - All Versions

hashtag
Cause

Cluster had its VIP address configured to be the same as that of one of the Master Nodes which resulted in conflict for the cluster to converge.

hashtag
Resolution

  1. Recreate the cluster with a VIP address separate from all the nodes within the cluster.

  2. Refer to the following articlearrow-up-right which provides detailed steps on how to create a Multi Master BareOS Cluster on Platform9 Managed Kubernetes.

hashtag
Additional Information

PreviousMaster Node on Cluster Recreation Unable to Converge as it Continues to Refer Older Cluster's Etcd DNextDocker: "Error response from daemon: client version 1.40 is too new. Maximum supported API version i

Last updated