Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

“No Datacenters are Available” after upgrading to vCloud Director 9.1 (53319)

Last Updated: 2/7/2019Categories: How toTotal Views: 3361Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

"No Datacenters are Available" error is present when accessing https:///tenant/org.vcd-fqdn"

"No Datacenters are Available" error is present after upgrading vCloud Director when accessing the Tenant UI.

Purpose

This article provides an overview on how to verify why the vCloud Director Cell cannot interact with the Public API Endpoint.

vCloud Director cannot interact with the Public API Endpoint for two reasons:

Incorrectly configured Certificates

Network Access to the Public API Endpoint

Resolution

Incorrectly configured Certificates

1. Ensure the Certificates have a correctly configured Subject Alternative Name (SAN).
1. Connect to a machine with OpenSSL installed
2. Run the command openssl s_client -connect <HTTPS REST API base URL>:443 | openssl x509 -noout -text | grep DNS

3. If you are connecting to vCloud Director with an FQDN or IP that is not present in the output, you may need to reconfigure your certificates.

For more information, see Generating SSL certificates for VMware vCloud Director

2. Ensure the Public Addresses Section is filled out correctly

1. Login to to the vCloud Director UI as a System Administrator
2. Click Administration
3. Click Public Addresses
4. Click Customize Public Endpoints
5. In the "API" section fill in your appropriate values for
5.1 HTTP Base URL
5.2 HTTPS REST API base URL
5.3 Certificate chain
If unsure, run the command openssl s_client -showcerts -connect <HTTPS REST API base URL> | sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p'
6. Click Apply

Network Access to the Public API Endpoint

Ensure connectivity from all Cells within the vCloud Director Server Group, to the Address specified in HTTPS REST API base URL section of the Public Addresses.
Note: You can use commands such as Telnet, and cURL to verify connectivity to the HTTPS Endpoint over port 443, or another port if the Default is not being used.

There may be an internal requirement that restricts the Cells from being able to access the Public Addresses.
In this instance, you can edit the Cell's Host File to redirect API Requests to itself rather than trying to contact the Public Addresses.

1. SSH to the vCloud Director Cell
2. Login as root
3. Backup the file /etc/hosts
4. Edit the file /etc/hosts
5. Add an entry in the format <Cell HTTP Interface IP> <HTTPS REST API base URL>
6. Save the File
7. Perform a Ping Command against the HTTPS REST API base URL and verify that the value returned is the Cell HTTP Interface IP
8. Repeat steps 1-7 above for all subsequent Cells.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Director for Service Provider

VMware Cloud Director

Related Versions:

VMware Cloud Director for Service Provider 9.0.x

Take Our Survey

Support Assistant