> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmk/how-to/master-node-is-failing-to-attach-to-existing-cluster-and-cluster.md).

# Master Node Fails to Attach to an Existing Cluster and UI Shows "Quorum Achieved with a tolerance 1"

## Problem

Master node gets failed to attach to an existing cluster. While adding a new master node to a cluster we see "Quorum Achieved with a tolerance 1" message warning as shown below screenshot.

<figure><img src="https://978681485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzyQCMA9ICq40g4F8hWJi%2Fuploads%2Fgit-blob-290f185a5f4bad21e53c9262b7d9b308a5d1c9b8%2F3s7xkiputa4p4sdu4yglpt6pes9afgg550z0hqb99op2z558zkc8lqwef3v1nj2p.png?alt=media" alt=""><figcaption></figcaption></figure>

## Environment

* Platform9 Managed Kubernetes - v5.6.0 and Higher

Cluster has two master nodes attached already and third master node needs to be attached.

## Cause

ETCD member cluster has older member data in database, which doesn't allow new master member to get attached to the cluster. Etcd logs shows below error "failed to reach the peer"

{% tabs %}
{% tab title="Etcd log on master node" %}

```javascript
{"log":"{\"level\":\"warn\",\"ts\":\"2023-02 17T03:53:28.271Z\",\"caller\":\"etcdserver/cluster_util.go:315\",\"msg\":\"failed to reach the peer URL\",\"address\":\"https://<IP>:2380/version\",\"remote-mem
ber-id\":\"<member-id>\",\"error\":\"Get https://<IP>:2380/version: dial tcp <IP>:2380: i/o timeout\"}<br>","stream":"stderr","time":"2023-02-17T03:53:28.27169764Z"}
{"log":"{\"level\":\"warn\",\"ts\":\"2023-02-17T03:53:28.271Z\",\"caller\":\"etcdserver/cluster_util.go:168\",\"msg\":\"failed to get version\",\"remote-member-id\":\"<member-id>\",\"error\":\"Get https://<IP>:2380/version: dial tcp <IP>:2380: i/o timeout\"}<br>","stream":"stderr","time":"2023-02-17T03:53:28.271755901Z"}
{"log":"{\"level\":\"warn\",\"ts\":\"2023-02-17T03:53:28.558Z\",\"caller\":\"rafthttp/peer.go:267\",\"msg\":\"dropped internal Raft message since sending buffer is full (overloaded network)\",\"message-type\":\"MsgHeartbeat\",\"local-member-id\":\"<Local-member-id>\",\"from\":\"<Local-member-id>\",\"remote-peer-id\":\"<member-id>\",\"remote-peer-active\":false}<br>","stream":"stderr","time":"2023-02-17T03:53:28.55946179Z"}
```

{% endtab %}
{% endtabs %}

## Resolution

Please follow below steps on Healthy master nodes:

1. Check if etcd member endpoint list has older member details present in it, by running endpoint status command on etcd container as shown below

{% tabs %}
{% tab title="On ETCD container" %}

```javascript
# sudo /opt/pf9/pf9-kube/bin/nerdctl -n k8s.io ps
# sudo /opt/pf9/pf9-kube/bin/nerdctl -n k8s.io exec -it etcd -- etcdctl --cacert=/certs/etcd/peer/ca.crt --cert=/certs/etcd/client/request.crt --key=/certs/etcd/client/request.key endpoint status --cluster -w=table
```

{% endtab %}
{% endtabs %}

2. If older entry is present, then run below command to remove stale entry from etcd database.

{% tabs %}
{% tab title="Remove stale ETCD member entry" %}

```javascript
# sudo /opt/pf9/pf9-kube/bin/nerdctl -n k8s.io exec -it etcd -- etcdctl --cacert=/certs/etcd/peer/ca.crt --cert=/certs/etcd/client/request.crt --key=/certs/etcd/client/request.key member remove <ID>
```

{% endtab %}
{% endtabs %}

3. Retry attaching a master node to existing cluster. Now, it should successfully get attached to master node.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://platform9.com/kb/pmk/how-to/master-node-is-failing-to-attach-to-existing-cluster-and-cluster.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.