Symptoms:
VMware Cloud Foundation 5.x
The issue is caused by
the https://<NSX_Manager_fqdn>/ui/api/v1/nsxt-clusters returns incomplete response.
The UI expects a structure that looks like this (for voew1nxl41p.oneadr.net NSXT cluster):{ "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx", "vipFqdn": "NSX_Manager_fqdn", .... "isShared": true, "isShareable": true, "isVlcmCompatible": false <-- this one is important}
but gets back this
{ "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx", "vipFqdn": "NSX_Manager_fqdn", .... "isShared": true, "isShareable": true, }
The "isVlcmCompatible" property is missing from the data.
As the isVlcmCompatible is missing, the UI cannot correctly identify the existing nsxt cluster is suitable for new domain creation.
Broadcom Engineering is aware about the issue and currently working to fix it.
Workaround:
Workload Domains in VMware Cloud Foundation
https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-5-2-and-earlier/5-1/getting-started-with-vcf-5-1/cloud-foundation-architecture/workload-domains-in-vmware-cloud-foundation.html
This is the create VI API documentation which you need to follow in order to prepare the creation VI json spec:
https://developer.broadcom.com/xapis/vmware-cloud-foundation-api/latest/domains/#_usecase_createdomain
Deploy a VI Workload Domain Using the VMware Cloud Foundation API
https://techdocs.broadcom.com/it/it/vmware-cis/vcf/vcf-5-2-and-earlier/4-5/administering/working-with-workload-domains-admin/about-virtual-infrastructure-workload-domains-admin/deploy-a-vi-workload-domain-using-the-vmware-cloud-foundation-api-admin.html