Add Host workflow hangs on "Remediate ESXi Host(s) to be Compliant with Cluster's Image" before failing. with message:
Applying personality to cluster domain-c8 failed with error: Monitor compliance task detail failed for task id: xxxxxx
vCenter compliance checks take over 5 minutes during Add Host operation. Compliance check shows: Host status is unknown:
The domainmanager.log shows:
2023-05-17T18:44:41.382+0000 ERROR [vcf_dm,006a287d3dc5466f,575d] [c.v.e.s.o.model.error.ErrorFactory,dm-exec-15] [RNGDVA] VLCM_REMEDIATE_PERSONALITY_FAILED Exception thrown when remediating cluster com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Exception thrown when remediating cluster at com.vmware.vcf.common.contract.fsm.actions.impl.ApplyVlcmAction.execute(ApplyVlcmAction.java:225) at com.vmware.vcf.common.contract.fsm.actions.impl.ApplyVlcmAction.execute(ApplyVlcmAction.java:58) ... ... Caused by: java.lang.RuntimeException: Monitor compliance task detail failed for task id: 526540bc-42c6-80b2-6a09-37bfb3bb7f7c:com.vmware.esx.settings.clusters.software at com.vmware.vcf.vapi.vsphere.PersonalityImageManager.getClusterComplianceDetail(PersonalityImageManager.java:650) at com.vmware.vcf.vapi.vsphere.PersonalityImageManager.getClusterComplianceDetail(PersonalityImageManager.java:633) at com.vmware.vcf.vapi.vsphere.PersonalityImageManager.getClusterComplianceFromTaskId(PersonalityImageManager.java:621) at com.vmware.vcf.vapi.vsphere.PersonalityImageManager.verifyCompliance(PersonalityImageManager.java:471) at com.vmware.vcf.vapi.vsphere.PersonalityImageManager.verifyCompliance(PersonalityImageManager.java:482) at com.vmware.vcf.common.contract.fsm.actions.impl.ApplyVlcmAction.execute(ApplyVlcmAction.java:136) ... 17 common frames omitted
Since the vCenter compliance checks are taking a significant amount of time to complete, the workflow is not returning to the domainmanager to continue the add host workflow. This causes an exception when remediating the cluster.
Please contact Global Support if you can not upgrade and would like to preform a workaround of this issue.