Scale out operations may fail in SSPi if VC object names are modified

Products

• VMware vDefend Firewall
• VMware vDefend Firewall with Advanced Threat Prevention

Issue/Introduction

After change vCenter object name, SSP workload cluster is unhealthy. SSP Installer operations like "edit deployment size"  time out. In the SSP workload cluster, pods in the "vmware-system-csi" namespace are crashing. 

 

vCenter objects include -->  Datacenter, Cluster, Datastore, Storage Policy. Resource Pool, Distributed Switch, Port group. 

 

csi-node logs will show the below symptoms :

k -n vmware-system-csi logs vsphere-csi-node-w6wfz

E0807 06:45:02.052394       1 main.go:103] Registration process failed with error: RegisterPlugin error -- plugin registration failed with err: rpc error: code = Internal desc = failed to retrieve topology information for Node: "secop-controller-xxxx". Error: "failed to retrieve nodeVM \"421f4adf-f705-26c8-1fdf-9b5d261ee38e\" using the node manager. Error: failed to fetch datacenters for vc xx.xx.xx with err: datacenter 'Datacenter-1' not found", restarting registration container.

 

Environment

vDefend SSP Installer 5.0

Cause

vDefend SSP Installer 5.0 is using vCenter object name in the workload cluster. If vCenter object name is changed, some resources in the SSP workload cluster might fail to sync with the vCenter

 

Resolution

Please refer SSPI Instance page and change vCenter object name back to old names