# Rollback LTS2 5.6

If the upgrade from LTS2 patch2 to LTS2 patch4 to SMCP fails then follow the rollback procedure, assuming [backup](https://github.com/platform9/pcd-docs-gitbook/blob/main/PEC/backup-guide/README.md) is already taken:

1. Download and install `5.9` artifacts.

{% hint style="info" %}
**Note:**

Ensure older 5.6 artifacts, especially /opt/pf9/airctl/pf9-kube/pf9-kube.tar.gz and /opt/pf9/airctl/nodelet/nodelet.tar.gz are renamed or copied to some other location, as the installation of the 5.9 artifacts may override those
{% endhint %}

2. Delete mgmt cluster

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

```bash
airctl stop
airctl unconfigure-du --force 
airctl advanced-ddu delete-mgmt
```

{% endtab %}
{% endtabs %}

3. Update the nodelet-bootstrap-config file by adding the `5.6` kubedu and nodelet images as part of userImages field.

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

```bash
userImages:
- /home/centos/patch2/kubedu-imgs-v-5.6.xxx.tar.gz
- /home/centos/patch4/kubedu-imgs-v-5.6.xxx.tar.gz
```

{% endtab %}
{% endtabs %}

4. Rename `/opt/pf9/airctl/conf/helm_charts/consul-0.24.0.tgz` to `consul-1.2.0.tgz` .

**Note:**

Move/Rename the original consul-1.2.0.tgz to some other location.

5. Run airctl [restore](https://github.com/platform9/pcd-docs-gitbook/blob/main/PEC/restore-guide/README.md).

{% hint style="info" %}
**Note:**

We can seamlessly upgrade to LTS2-patch4 (using the process mentioned under the [upgrade guide](https://github.com/platform9/pcd-docs-gitbook/blob/main/PEC/Upgrade-guide/README.md)), if the LTS2-patch2 setup is restored using the above procedure.

As we are using 5.9 airctl binary here, we will not face [this issue mentioned in the kb](https://platform9.com/kb/PEC/while-upgrade-from-lts2-patch2-to-scmp--management-plane-cluster).
{% endhint %}

6. Later move to SMCP, follow the [upgrading to SMCP guide](https://github.com/platform9/pcd-docs-gitbook/blob/main/PEC/upgrade-smcp/README.md).

After restore, we should be able to login to UI and view the existing workload clusters.

{% hint style="warning" %}
**Consul Issue:**

After restore, errors seen in the consul pod saying 'ACL not found', which are harmless and can be ignored.

So, we are currently skipping the consul upgrade in the upgrade step and installing the upgraded consul in the restore process itself.
{% endhint %}