Deployment of the NFS Client may fails if a different name other than the default name is used for the NFS Client Storage Class Add-on

Products

• VMware Telco Cloud Automation

Issue/Introduction

When deploying the nfs-client addon prior to TCA 3.2, we suggest using names starting with "nfs-client", such as "nfs-client-region-1". Failing to do so may result in a persistent abnormal state for the nfs-client addon.

Environment

2.x ,3.0.x ,3.1.x

 

 

Resolution

When deploying the nfs-client addon prior to TCA 3.2, we suggest using names starting with "nfs-client", such as "nfs-client-region-1". Failing to do so may result in a persistent abnormal state for the nfs-client addon.

If you need to deploy multiple nfs-client instances, you can append different custom characters to the "nfs-client" string for differentiation. This is currently the best practice for deploying nfs-client addons.

If you insist on using names that do not start with "nfs-client", to ensure a successful deployment, you will need to:
1. Initially deploy the nfs-client addon with a name starting with "nfs-client".
2. Once the deployment is successful, edit the addon name to your desired one.

Note:
When upgrading or editing the cluster etc, the status of addon may become abnormal again, but it essentially does not affect the functionality of the nfs-client addon,  so you can choose to ignore the addon status. If not, you may need to change the name back to "nfs-client", once the addon status is normal, rename it back to your desired name.

This issue is fixed in TCA 3.2