VMware Cloud Community
senwebtek
Contributor
Contributor

vCLS in 7.03 cluster services not starting

I have a problem when starting up a cluster using the 'Restart Cluster' command after rebooting the cluster. The vCLSs get provisioned on vSAN but never start. I've tried putting the cluster in 'retreat mode' and taking it back out but that does nothing. Skyline Health Diagnostic doesn't show anything and neither does the built in Skyline Health online check. Of course, I can't manually start the vCLSs because they are system managed vms. Is there a way to force startup of these vms or is there anywhere I can look to find out what is preventing the vCLS vms from starting? I don't see any errors except the 'unhealthy state of vSphere Cluster Services' in the All Issues section under 'Monitor'

EDIT: After restarting vCenter, the vCLSs aren't being deployed at all; storage appears OK

EDIT2: Here are some relevant log entries for one of the vCLSs that won't start:

2022-03-18T09:21:19.858-05:00 info vpxd[05804] [Originator@6876 sub=MoCluster] vCS VM [vim.VirtualMachine:vm-5008,vCLS-174a8c2c-d62a-4353-9e5e-e6bc70a4f0d1] being loaded during VPXD restart was not powered on
2022-03-18T09:21:20.933-05:00 info vpxd[05804] [Originator@6876 sub=TenantManager] managedEntity = vCLS-174a8c2c-d62a-4353-9e5e-e6bc70a4f0d1
2022-03-18T09:21:24.343-05:00 info vpxd[06022] [Originator@6876 sub=MoCluster opID=SWI-3113c398] Received VM state change for HDCS VM [vim.VirtualMachine:vm-5008,vCLS-174a8c2c-d62a-4353-9e5e-e6bc70a4f0d1] oldConnState: 1, newConnState: 3, oldPowerState: 0, newPowerState: 0
2022-03-18T09:21:25.373-05:00 info vpxd[06068] [Originator@6876 sub=MoCluster opID=HostSync-host-1018-94dc561] Received VM state change for HDCS VM [vim.VirtualMachine:vm-5008,vCLS-174a8c2c-d62a-4353-9e5e-e6bc70a4f0d1] oldConnState: 3, newConnState: 1, oldPowerState: 0, newPowerState: 0
2022-03-18T09:22:31.667-05:00 info vpxd[06815] [Originator@6876 sub=MoCluster opID=HostSync-host-1018-6f863a83] Received VM state change for HDCS VM [vim.VirtualMachine:vm-5008,vCLS-174a8c2c-d62a-4353-9e5e-e6bc70a4f0d1] oldConnState: 1, newConnState: 3, oldPowerState: 0, newPowerState: 0

 EDIT 3: I managed to get the vCLSs to start by restarting vCenter and then putting cluster in 'retreat' mode and then taking it back out; don't know why this is happening since it seems that sometimes this works and sometimes it doesn't. This happens even though I've done a clean cluster shutdown and restart using the vSAN cluster commands.

0 Kudos
0 Replies