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

VIO How to troubleshoot a "No valid host was found. There are not enough hosts available." error. (59345)

Last Updated: 9/4/2020Categories: TroubleshootingTotal Views: 5433Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

An instance is launched, and it will promptly fail.

The error returned in the Horizon UI of VMware Integrated OpenStack is: "No valid host was found. There are not enough hosts available."

Cause

The instance ID or request ID must be tracked through the logs to find the true cause of the errors. For services nova-scheduler will have the most details.

The number of available hosts that OpenStack can deploy the instance to is zero. Here's a list of the example of causes:

If nova-compute is down as a service we will start with zero hosts to deploy to.

Resource quotas could be met.

A custom value in image or flavor metadata could be invalidating available compute or datastores.

Resolution

Note:  The message returned is generic and further troubleshooting must be done for the root cause.
There are several areas to check in 5.1:

On the compute node where the instance was attempting to launch, review the /var/log/nova/nova-compute.log for errors related to the request id.

There is a possibility all hosts were filtered in which we need to track the request ID or the instance ID in the /var/log/nova/nova-scheduler.log on the controllers.

Check the services and components of VMware Integrated OpenStack for errors.

Are there any ESXi host or storage failures?

Is communication working with the NSX Manager or vCenter?

Is the failure only happening with a specific message or metadata requirement?

In 6.0 or 7.x for VMware Integrated OpenStack:

Collect the list of pods with: osctl get pods

Find the request ID for the instance in the nova compute pod with: osctl log<compute pod UUID>

Then search the nova-scheduler pod's logs the request, and find the result that invalidated available hosts: osctl log <nova-scheduler pod UUID>

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
如何从群集中移除 vRealize Automation 设备 (2149866)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Integrated OpenStack

Related Versions:

VMware Integrated Openstack 7.x

VMware Integrated OpenStack 6.x

VMware Integrated OpenStack 5.x

VMware Integrated OpenStack 4.x

Take Our Survey

Support Assistant