From Recent Tasks, we see that it failed at "Generate inputs for configuring NSX Manager after import" with the cause: "vCenter with the name ##### not found in the inventory"
VCF 9.x
This is because of a case-sensitivity mismatch in the vCenter FQDN provided in the input specification.
The domainmanager.log reported a runtime exception during the GeneratePostNsxImportConfigurationsInputAction task:
java.lang.RuntimeException: vCenter with the name ####### not found in the inventory
ERROR [vcf_dm,###########,eb44] [c.v.e.s.o.model.error.ErrorFactory,dm-exec-11] [7SUVV2] VCF_ERROR_INTERNA
L_SERVER_ERROR Invocation of prefix '' part of task GeneratePostNsxImportConfigurationsInputAction in plugin ViDomainServicePlugin failed with exception.
com.vmware.evo.sddc.common.core.error.InternalServerErrorException: Invocation of prefix '' part of task GeneratePostNsxImportConfigurationsInputAction in pl
ugin ViDomainServicePlugin failed with exception.
at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.invokeMethod(ProcessingTaskSubscriber.java:450)
at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.processTask(ProcessingTaskSubscriber.java:517)
at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.accept(ProcessingTaskSubscriber.java:128)
at jdk.internal.reflect.GeneratedMethodAccessor332.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:569)
at com.google.common.eventbus.Subscriber.invokeSubscriberMethod(Subscriber.java:85)
at com.google.common.eventbus.Subscriber.lambda$dispatchEvent$0(Subscriber.java:71)
at com.vmware.vcf.common.tracing.TraceRunnable.run(TraceRunnable.java:63)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: java.lang.RuntimeException: vCenter with the name ######## not found in the inventory
The environment (DNS, PNID, and DB tables) used the capitalized name ##########, but the brownfield input spec used lowercase ###########
To resolve the inconsistency, the domain status must be manually transitioned in the SDDC Manager database to allow the Brownfield Import workflow to re-initialize and overwrite the stale metadata.
Steps:
Take a virtual machine snapshot of the SDDC Manager.
Access the SDDC Manager via SSH as root and enter the PostgreSQL console:
psql -h localhost -U postgres -d platform
UPDATE domain SET status = 'ACTIVATING' WHERE id = '[Target_Domain_ID]';
Trigger a fresh Brownfield Import workflow using the properly cased FQDN in the input spec.