Failed to get network info. Http failure response for https://sddc-manager.example.com/ui/api/v1/clusters/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx4435/network/queries/yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyya40e: 500 Internal Server Error
INFO [vcf_dm,e26f6ee5ff524f82,3fd5] [c.v.v.c.n.s.c.c.NsxtManagerTransportNodeOperationsPolicyHandler,dm-exec-6] nsx-policy-transportnode: Getting the transport node by name hostname.example.com using the policy API.
ERROR [vcf_dm,e26f6ee5ff524f82,3fd5] [c.v.e.s.c.s.ClusterNetworkConfigFetcher,dm-exec-6] Unable to get healthy transport node for healthy host hostname.example.com
VMware Cloud Foundation 5.1
SDDC Manager is using the wrong API library to communicate with Federated NSX Managers.
Issue is fixed in VCF 5.2
As a workaround, policy APIs (introduced in 5.1) can be turned off, and add host(s) operation be performed.
Steps to apply the workaround:
vi /etc/vmware/vcf/domainmanager/application-prod.properties
nsxt.base.version.policy=4.2.0.0.0-0
Esc > :wq!
systemctl restart domainmanager
systemctl status domainmanager -l
vi /etc/vmware/vcf/domainmanager/application-prod.properties
nsxt.base.version.policy=4.2.0.0.0-0
Esc > :wq!
systemctl restart domainmanager
systemctl status domainmanager -l