ERROR: "Existence check for network in the given vCenter, data center and cluster" when deploying VMware Cloud Foundations Operations for Network

Products

• VCF Operations

Issue/Introduction

• The VMware Cloud Foundation (VCF) Operations for Network deployment pre-check fails with the errors below:
  
  Existence check for a cluster in the given vCenter and data center.
Check if the given cluster is existing in the vCenter and data center.
 

Existence check for datastore in the given vCenter, data center and cluster.
[vc=VC NAME, cluster=CLUSTER NAME, datastore=DATASTORE NAME]
Check if the datastore exists in the given vCenter, data center and cluster.

Existence check for network in the given vCenter, data center and cluster.
DATACENTER NAME
Check if network exists in the given vCenter, data center and cluster.

 
Admin role permission check for the cluster in the given vCenter and data center.
CLUSTER NAME
Check if the admin role permissions are available on the resources selected in the given vCenter and data center.
• The vCenter (VC) cluster has been recently renamed  via SDDC Manager.
• The new VC cluster name is correctly shown on VC inventory, VCF Operations inventory and SDDC manager inventory.
• The cluster name reported on the errors above is the old cluster name.
• When trying to deploy VCF Operations for Network in the "Infrastructure" tab under "Select Cluster" the old cluster name is reported
• In /var/log/vrlcm/vmware_vrlcm.log on Fleet management appliance we see the error below:

  2026-06-03T09:05:31.265Z ERROR vrlcm[1619] [pool-3-thread-39] [c.v.v.l.d.c.v.i.DataStoreValidator]  -- Exception occurred while validating datastore existence
java.lang.NullPointerException: null
        at com.vmware.vrealize.lcm.drivers.vsphere65.vlsi.utils.CoreUtility.getdataStoreFromCluster(CoreUtility.java:2650) ~[vmlcm-vsphereplugin-driver-9.0.2.0-SNAPSHOT.jar!/:?]
        at com.vmware.vrealize.lcm.drivers.commonplugin.validator.impl.DataStoreValidator.validateDataStoreExistence(DataStoreValidator.java:126) [vmlcm-commonplugin-common-9.0.2.0-SNAPSHOT.jar!/:?]
        at com.vmware.vrealize.lcm.drivers.commonplugin.validator.impl.DataStoreValidator.validateDataStore(DataStoreValidator.java:114) [vmlcm-commonplugin-common-9.0.2.0-SNAPSHOT.jar!/:?]
        at com.vmware.vrealize.lcm.drivers.commonplugin.validator.impl.DataStoreValidator.validateDatastore(DataStoreValidator.java:70) [vmlcm-commonplugin-common-9.0.2.0-SNAPSHOT.jar!/:?]
        at com.vmware.vrealize.lcm.drivers.commonplugin.task.InfraValidationTask.execute(InfraValidationTask.java:130) [vmlcm-commonplugin-core-9.0.2.0-SNAPSHOT.jar!/:?]
        at com.vmware.vrealize.lcm.automata.core.TaskThread.run(TaskThread.java:62) [vmlcm-engineservice-core-9.0.2.0-SNAPSHOT.jar!/:?]
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:?]
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:?]
        at java.base/java.lang.Thread.run(Unknown Source) [?:?]

Environment

VMware Cloud Foundation 9.0

Cause

This is expected behavior since the VC Cluster information is updated in SDDC Manager.

Resolution

Triggering VC inventory sync from Fleet LCM :

1. On VCF Operations select  Fleet Management > Lifecycle > VCF Management > Settings > Deployment Targets 
2. Then select "Refresh data collection" (refresh icon in the VC table).
3. Post refresh is complete, retry the failed deployment by selecting new cluster name.