Deployment failure during management domain installation: Error LCMVROPSSYSTEM29002
Article ID: 439870
Updated On:
Products
VCF Operations
Issue/Introduction
- Greenfield deployment of management domain using VCF installer is is failing with the following error:
LCMVROPSSYSTEM29002 - /var/log/vrlcm/vmware-vrlcm.log in Fleet Management shows the following error:
[{"messageId":"LCMVROPSSYSTEM29002","message":"Operations collector group operation failure","eventId":"########-####-####-####-############","retry":true,"exceptionMessage":"Wait timeout, Cloud Proxy node didn't join the Operations cluster, retry after sometime.","exceptionStackTrace":"com.vmware.vrealize.lcm.plugin.common.vrops.exceptions.CollectorGroupOperationsException: Wait timeout, Cloud Proxy node didn't join the Operations cluster, retry after sometime.\n\tat com.vmware.vrealize.lcm.plugin.core.vrops.tasks.VropsOnPremCpNodeWaitForStartTask.execute(VropsOnPremCpNodeWaitForStartTask.java:67)\n\tat com.vmware.vrealize.lcm.plugin.core.vrops.tasks.VropsOnPremCpNodeWaitForStartTask.retry(VropsOnPremCpNodeWaitForStartTask.java:122)\n\tat com.vmware.vrealize.lcm.automata.core.TaskThread.run(TaskThread.java:60)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)\n\tat java.base/java.lang.Thread.run(Unknown Source)\n","localizedMessageId":"VROPS_ON_PREM_CP_NODE_WAIT_FOR_START_TASK_00002","parameters":null,"properties":{"deleteVm":"false"}}] - Splash screen of Cloud Proxy on boot up shows the error:
[FAILED] Failed to start Wait for Network to be Configured. - Launching the web/remote console for the cloud proxy shows the error "
Please wait. Establishing connection with VMware Cloud Foundation Operations/ 30" - Signing into Cloud Proxy web/remote console with root credentials shows
root@localhost - Running
journalctl -xeu haproxy.serviceon the cloud proxy returns ntp errors :Apr 29 16:31:12 <cpFQDN> systemd[1]: ntpd.service: Failed with result 'exit-code'. Apr 29 16:31:12 <cpFQDN> systemd[1]: Failed to start Network Time Service. Apr 29 16:31:12 <cpFQDN> systemd[1]: ntpd.service: Scheduled restart job, restart counter is at 5. Apr 29 16:31:12 <cpFQDN> systemd[1]: Stopped Network Time Service. Apr 29 16:31:12 <cpFQDN> systemd[1]: ntpd.service: Start request repeated too quickly. - Running
nslookupon the cloud proxy returns no results for VCF operations nodes
Environment
VCF Operations 9.x
Cause
There is a connectivity gap where the Cloud Proxy node is isolated from required DNS, NTP, or external Broadcom URLs causing the deployment to fail. Can also occur if the deployment environment has strict egress filtering, the Cloud Proxy may fail to resolve the FQDNs of management nodes or reach external synchronization sources. This results in a deployment timeout in the VCF Installer.
Resolution
Ensure the firewall allows the Cloud Proxy to communicate externally for DNS (Port 53) and NTP (Port 123)
Additional Information
Feedback
Yes
No
Powered by
