> 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/pmk-cluster-upgrade-fails-due-to-host-in-converge-failed-state.md).

# PMK Cluster Upgrade Fails Due to Host in Converge Failed State

## Problem

PMK Cluster upgrade task fails due to one or more hosts going to "Converge Failed" state.

## Environment

* Platform9 Managed Kubernetes - v4.5 and Higher
* Ubuntu OS 18.04

## Cause

This could be due to an error with the apt package manager on the host(s) while removing the pf9-kube role during the cluster upgrade.

## Resolution

1\. Check the *hostagent.log* entries on the host corresponding to the time of failure. Verify that the error message is similar to the one shown below:

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

```none
2021-04-22 00:03:30,497 - pf9_app_db.py ERROR - Erase command failed : sudo /opt/pf9/hostagent/bin/pf9-apt erase pf9-kube. Return code: 1, stdout: , stderr: Failed to erase package: pf9-kubeTraceback (most recent call last):...apt_pkg.Error: E:dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
```

{% endtab %}
{% endtabs %}

2\. Run the following command on the host:

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

```none
$ sudo dpkg --configure -a
```

{% endtab %}
{% endtabs %}

3\. Restart the pf9-hostagent service on the host:

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

```none
$ sudo systemctl restart pf9-hostagent
```

{% endtab %}
{% endtabs %}

Note: In case after performing the above steps the host is still in "Converge Failed" state, contact Platform9 Support for further assistance.


---

# 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 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/solutions/pmk-cluster-upgrade-fails-due-to-host-in-converge-failed-state.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 `automate deployments from our CI pipeline` 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.