DEBUG [vcf_om,695e##############b13d,a6c0] [c.v.e.s.e.h.LocalizableRuntimeExceptionHandler,http-nio-127.0.0.1-7300-exec-2] Processing localizable exception Validation of data source of type INTERNAL_MIXED_SDDC_MANAGER
and address <vcfFQDN> failed.
ERROR [vcf_om,695e#################b13d,a6c0] [c.v.e.s.e.h.LocalizableRuntimeExceptionHandler,http-nio-127.0.0.1-7300-exec-2] [GJJEL5] BASELINER_DATASOURCE_VALIDATION_FAILED Validation of data source of type INTERNAL_MIXED_SDDC_MANAGER and address <VCFFQDN> failed.
com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Validation of data source of type INTERNAL_MIXED_SDDC_MANAGER and address <VCFFQDN>failed.
c.common.validation.errors.messages","validation.taskId":"0a0###2f-9###-17##-81##-99d9#######25"},"message":"Existing vSphere is eligible to be converted to a VCF domain","nestedErrors":[{"errorCode":"VMWARE_COMPONENT_IP_NOT_IN_VC_MGMT_NETWORK.info","arguments":["VCF Operations Node","<VCFFQDN>","1"VcManager vCenter vpxd service is started","remediationMessage":"null"}]},{"errorCode":"BROWNFIELD_VSPHERE_VALIDATION_STATUS.info","arguments":[],"context":{"severity":"INFO","bundleName":"com.vmware.evo.sddc.common.validation.errors.messages","validation.taskId":"0a0####-9##-17##2-8##b-9######0025"},"message":"Existing vSphere is eligible to be converted to a VCF domain","nestedErrors":[{"errorCode":"VMWARE_COMPONENT_IP_NOT_IN_VC_MGMT_NETWORK.info","arguments":["VCF Operations Node","<VCFFQDN>","#.#.#.#","#.#.#.#/24"],"context":{"#.#.#.#","#.#.#.#/24"],"context":{"severity":"INFO","bundleName":"com.vmware.evo.sddc.common.validation.errors.m
VMware Cloud Foundation 9.x
The root cause was a Fully Qualified Domain Name (FQDN) reuse conflict. The FQDN of vcf was already assigned to the VCF Installer appliance, which was actively running the deployment wizard.The same FQDN was also configured for the VCF Operations Node during the deployment workflow.
As a result, the FQDN was already resolvable and pingable on the network before deployment began.
Assign a unique and dedicated FQDN to the VCF Operations Node that does not overlap with the FQDN used by the VCF Installer appliance.
Steps:
Once a unique FQDN/IP pair was assigned, the validation engine successfully verified network availability and routing.
The deployment proceeded without triggering the INTERNAL_MIXED_SDDC_MANAGER or IP-in-use validation errors.