Rollback LTS2 5.6

If the upgrade from LTS2 patch2 to LTS2 patch4 to SMCP fails then follow the rollback procedure, assuming backuparrow-up-right is already taken:

  1. Download and install 5.9 artifacts.

circle-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

  1. Delete mgmt cluster

airctl stop
airctl unconfigure-du --force 
airctl advanced-ddu delete-mgmt
  1. Update the nodelet-bootstrap-config file by adding the 5.6 kubedu and nodelet images as part of userImages field.

userImages:
- /home/centos/patch2/kubedu-imgs-v-5.6.xxx.tar.gz
- /home/centos/patch4/kubedu-imgs-v-5.6.xxx.tar.gz
  1. 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.

circle-info

Note:

We can seamlessly upgrade to LTS2-patch4 (using the process mentioned under the upgrade guidearrow-up-right), 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 kbarrow-up-right.

  1. Later move to SMCP, follow the upgrading to SMCP guidearrow-up-right.

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

circle-exclamation

Last updated

Was this helpful?