PVC attachment to application PODs fails after updating to TCA 3.2

Products

• VMware Telco Cloud Automation

Issue/Introduction

After upgrading to Telco Cloud Automation (TCA) 3.2, vSphere PVC attachment to application PODs fails and remains in a Pending state.  

• PVC attachment to pods are showing pending

Environment

TCA 3.2

Cause

cluster.local/nfs-client-nfs-client-provisioner is the default provisioned name in 2.3 for storage class. When updating TCA from 2.3 to 3.2, old storage class should be deleted and new one should be created. This issue is caused by a change in the format of values.yaml in the secret, leading to the original StorageClass was not deleted and recreated. In 2.3.0, the top-level attribute name in values.yaml was 'storageClass', not 'storageClasses'

 

Resolution

To fix the issue you can follow below solutions:

Solution 1:

1. Click already deployed "nfs-client" add-on and the "edit"
2. Do not modify any values, click save

After the nfs-client status reaches ready, the deleted storage class will be automatically created, and the provisioner name will be consistent with the pod

Solution 2:

• 1. Re-deploy nfs-client addon