When you deploy VCF Operations for Logs version 9.0.2 via the Fleet Management, the task fails at Stage 9. The following error message appears in the SDDC Manager UI or logs:
Error Code: LCMVROPSYSTEM25000 Confirm that the specified node is a member of Operations cluster and the node is online and accessible Not able to connect to Operations node VCFOPS (The shortname)com.vmware.vrealize.lcm.plugin.common.vrops.exceptions.VropsAddressException: Not able to connect to Operations node lvariaops at com.vmware.vrealize.lcm.plugin.core.vrops.tasks.BaseConfigureVropsTask.init(BaseConfigureVropsTask.java:170) at com.vmware.vrealize.lcm.plugin.core.vrops.tasks.VropsCreateServiceAccountTask.execute(VropsCreateServiceAccountTask.java:69) at com.vmware.vrealize.lcm.automata.core.TaskThread.run(TaskThread.java:62) 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)
VCF Operations 9.0.x
VCF Operations for Logs 9.0.x
Fleet Management 9.0.x
This issue occurs because the VCF Operations appliance is configured with a short name (hostname only) instead of a Fully Qualified Domain Name (FQDN). This mismatch prevents the deployment process from successfully verifying the node's connectivity and cluster membership.
To resolve this issue, you must update the appliance hostname to the FQDN and synchronize the inventory:
Fleet Management > Lifecycle > VCF Management.VCF Operations and click Manage.Trigger Inventory Sync to synchronize the appliance data.Primary, Replica, Witness, expanding the VCF Operations section, and confirming the FQDN field displays the full domain name instead of the short name.VCF Operations for Logs deployment.