This issue can be hit once the Add Host operation is triggered post-vCenter certificate replacement via VCF certificate workflow, This article provides workaround to users.
Symptoms:
Post vCenter certificate rotation, ADD Host operation in SDDC Manager is failing with in Validate Compute Manager Status of the Domain in NSX Sub-Task
ERROR:
[c.v.v.c.f.p.n.a.ValidateComputeManagerStatusAction,dm-exec-3] Compute manager vcenter-1.rainpole.local status is not UP in NSX manager <NSX_FQDN>, Status returned is false
333364 2023-10-11T21:33:02.864+0000 ERROR [vcf_dm,81d5695e145a6096,30d5] [c.v.e.s.o.model.error.ErrorFactory,dm-exec-3] [F0BPLJ] COMPUTE_MANAGER_STATUS_IS_NOT_UP Status for the Compute manager <vCenter-FQDN> is not UP in the NSX manager <NSX_FQDN>
com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Status for the Compute manager <vCenter-FQDN> is not UP in the NSX manager <NSX_FQDN>
at com.vmware.vcf.common.fsm.plugins.nsxt.action.ValidateComputeManagerStatusAction.execute(ValidateComputeManagerStatusAction.java:100)
at com.vmware.vcf.common.fsm.plugins.nsxt.action.ValidateComputeManagerStatusAction.execute(ValidateComputeManagerStatusAction.java:34)
at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionState.invoke(FsmActionState.java:62)
at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionPlugin.invoke(FsmActionPlugin.java:159)
at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionPlugin.invoke(FsmActionPlugin.java:144)