> 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/solutions/new-nodes-are-unable-to-join-a-pmk-cluster.md).

# New Nodes are Unable to Join a PMK Cluster

## Problem

* Node scaleout fails. The node gets added to the management plane and is visible in the UI under cluster but not completely joined to the cluster.
* Below errors could be seen in the Nodeletd logs from the respective node.

{% tabs %}
{% tab title="Bash" %}

```bash
{"L":"INFO","T":"2022-09-23T06:23:25.113Z","C":"phases/phases.go:279","M":"--- /opt/pf9/pf9-kube/none_scripts/10-all-none-scripts.sh status at 2022-09-23 06:23:25 ---"}
{"L":"INFO","T":"2022-09-23T06:23:25.113Z","C":"phases/phases.go:279","M":"[2022-09-23 06:23:25] http proxy: http/s_proxy env vars not defined, no pf9-comms proxy configuration; skipping configuration"}
{"L":"INFO","T":"2022-09-23T06:23:25.113Z","C":"phases/phases.go:279","M":"[2022-09-23 06:23:25] unknown"}
{"L":"INFO","T":"2022-09-23T06:23:25.113Z","C":"phases/phases.go:279","M":"[2022-09-23 06:23:25] [DOCKER-DAEMON-FAIL] docker daemon is not running"}
{"L":"INFO","T":"2022-09-23T06:23:25.113Z","C":"phases/phases.go:279","M":"[2022-09-23 06:23:25] [DOCKER-DAEMON-FAIL] docker daemon is not running"}
{"L":"INFO","T":"2022-09-23T06:23:25.113Z","C":"nodelet/nodelet.go:418","M":"Submitting status update to Sunpike: localhost:8111"}
{"L":"INFO","T":"2022-09-23T06:23:25.156Z","C":"nodelet/nodelet.go:232","M":"pf9-kube is already stopped..."}
{"L":"INFO","T":"2022-09-23T06:23:25.156Z","C":"nodelet/nodelet.go:438","M":"Submitting status update to Sunpike and checking it for new config: localhost:8111"}
{"L":"INFO","T":"2022-09-23T06:23:25.177Z","C":"nodelet/nodelet.go:452","M":"Handling received HostSpec from Sunpike."}
{"L":"INFO","T":"2022-09-23T06:23:25.178Z","C":"nodelet/nodelet.go:475","M":"Received config from Sunpike has not changed compared to the current config."}
{"L":"INFO","T":"2022-09-23T06:23:25.179Z","C":"nodelet/nodelet.go:173","M":"Reconcile completed."}
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed Kubernetes - v4.3 and Higher

## Cause

* This condition could be seen when a cluster upgrade in past was not fully completed and got stuck in the middle due to some reason.
* The below could be seen in the Qbert database.

{% tabs %}
{% tab title="Bash" %}

```bash
"kubeRoleVersion": "1.19.6-pmk.1709",
  "minorUpgradeRoleVersion": "1.20.11-pmk.2032",
  "upgradingTo": "1.20.11-pmk.2032",
```

{% endtab %}
{% endtabs %}

## Resolution

* Login to the Management Plane UI and go to the clusters section. Scroll to the right to see if there's an option **Continue Upgrade** available for the respective cluster.
* Click on **Continue Upgrade** option so that the post upgrade is completed and the Qbert gets updated with the desired version.
* Post this operation is executed successfully, the scaled out node should be added to the cluster automatically and should be in `Ready` state.
* If not, restart PMK stack on the affected node using the following steps:

{% tabs %}
{% tab title="Bash" %}

```bash
# systemctl stop pf9-hostagent pf9-nodeletd
# /opt/pf9/nodelet/nodeletd phases stop
# systemctl start pf9-hostagent
```

{% endtab %}
{% endtabs %}

## Additional Information

Make sure that all the nodes that are part of the respective cluster are in **Connected** state for the **Continue Upgrade** to execute successfully.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://platform9.com/kb/pmk/solutions/new-nodes-are-unable-to-join-a-pmk-cluster.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.