Upgrading VMware Telco Cloud Service Assurance 2.3 to 2.4 on Azure Fails

This section provides you the troubleshooting procedure to fix the failure related to the redis-cluster application that causes the failure of upgrading VMware Telco Cloud Service Assurance 2.3 to 2.4 on Azure.

You must perform the following procedure to fix the failure related to the redis-cluster application and then upgrade VMware Telco Cloud Service Assurance 2.3 to 2.4 on Azure.

Procedure

1. Pause the redis-cluster application.

   kubectl patch app redis-cluster -n tcsa-system  --type "json" -p '[{"op":"add","path":"/spec/paused","value": true }]'

2. Run the kubectl get app redis-cluster command to verify the status of the redis-cluster application. It should be in Canceled/Paused state.
3. Delete the redis-cluster deployment.

   kubectl delete sts redis-cluster -n tcsa-system

4. Verify that all the redis-cluster pods are deleted by running the following command.

   kubectl get pods -A -n tcsa-system | grep redis-cluster

   If any redis-cluster pods are in the terminating state, then run the following command.   kubectl get pods -A -n tcsa-system | grep redis-cluster | awk '{ print $1}' | xargs kubectl delete pod -n tcsa-system  --force --grace-period=0

5. Delete all the Redis PVCs.

   for i in $(kubectl get pvc -n tcsa-system | grep redis-cluster | awk '{ print $1}') ; do kubectl delete pvc $i -n tcsa-system  ; done

6. Delete all the Redis PVs.

   for i in $(kubectl get pv | grep redis-cluster | awk '{ print $1}') ; do kubectl patch pv $i --type='json' -p='[{"op": "remove","path": "/spec/claimRef"}]' ; kubectl delete pv $i ; done

7. Unpause the redis-cluster application by removing the paused flag under specification.

   kubectl patch app redis-cluster -n tcsa-system  --type "json" -p '[{"op":"remove","path":"/spec/paused" }]'