Symptoms:
ERROR [vcf_dm,e84627b9aefdf52f,dba3] [c.v.e.s.o.d.i.OrchestratorDataImpl,http-nio-127.0.0.1-7200-exec-3] In OrchestratorDataImpl, failed to get execution
com.vmware.evo.sddc.orchestrator.model.error.ExecutionException: null
at com.vmware.evo.sddc.orchestrator.dal.impl.OrchestratorDataImpl.getExecutionContext(OrchestratorDataImpl.java:863)
at com.vmware.evo.sddc.orchestrator.core.OrchestratorImpl.getExecutionContext(OrchestratorImpl.java:469)
at com.vmware.evo.sddc.orchestrator.core.OrchestratorImpl.lambda$getExecutionContexts$2(OrchestratorImpl.java:442)
[...]
ERROR [vcf_dm,7c1f8557ba2f4047,ad60] [c.v.v.c.f.p.n.a.VerifyT0ToT1ConnectivityAction,dm-exec-18] Tier0-Tier1 connectivity check failed for Tier0 -f8eb27ef-bb8f-4f7a-b425-ce47a4924c3c df784ff9-d177-4cf9-a0f2-c659fee19a1a
ERROR [vcf_dm,7c1f8557ba2f4047,ad60] [c.v.e.s.o.model.error.ErrorFactory,dm-exec-18] [7CRSOB] T0_TO_T1_CONNECTIVITY_IS_INVALID T0 to T1 connectivity is not configured properly.
com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: T0 to T1 connectivity is not configured properly.
SDDC Manager 5.x
SDDC Manager 4.x
This is a know issue that occurs when a Tier-1 is linked to a VRF instead of directly connected to the Tier-0.
A fix to this issue has been applied in VCF version 5.2.0 and later
Note: If you can't upgrade contact VCF-GS support to provide a workaround.