While attempting to create a new VI Workload Domain in VMware Cloud Foundation (VCF) 9.x:
Detailed Diagnosis: Analysis of the operationsmanager logs and browser HAR files reveal a silent validation failure.
####-##-##T##:##:##.###+0000 ERROR [vcf_om,6a39788b1793035d5c2264f69b5033b6,9032] [c.v.v.c.n.s.impl.NsxtWs1bServiceImpl,ra-exec-5] Failed to fetch the OIDC end point info for null Failed to resolve 'null'
Error has been observed at the following site(s):
*__checkpoint ⇢ Request to GET https://null/api/v1/trust-management/oidc-uris [DefaultWebClient]
VCF 9.x
SDDC 9.x
A UI validator bug in VCF 9.x fails to render a "Subnet Mismatch" error when the NSX Manager appliances are placed on a different subnet than the vCenter Server. VCF 9.x architectural requirements mandate that all management components for a Workload Domain (vCenter and NSX Managers) must reside on the same management subnet. If the NSX Manager FQDNs resolve to an IP range that differs from the vCenter subnet (e.g., vCenter on 10.5.200.x and NSX on 10.6.200.x), the UI validator blocks progress. Due to a software defect , the UI fails to display the specific error message for this mismatch.
To resolve this issue, the NSX Manager components must be aligned with the vCenter subnet:
Deploying management components on disparate subnets is not a supported configuration in VCF 9.x for new Workload Domain deployments.