openstack kilo can't launch a instance nova-conductor's and nova-compute's log have error

Bug #1467734 reported by elrondwang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Undecided
Unassigned

Bug Description

Bug Description

environment: openstack kilo centos7 tree node(controller nova neutron)

when I launch a instance in dashborad,it masks a mistake.the prompt is: No valid host was found. There are not enough hosts available.].

In controller node /var/log/nova/nova-conductor.log shows:
File "/usr/lib/python2.7/site-packages/nova/scheduler/manager.py", line 86, in select_destinations
    filter_properties)

  File "/usr/lib/python2.7/site-packages/nova/scheduler/filter_scheduler.py", line 80, in select_destinations
    raise exception.NoValidHost(reason=reason)

NoValidHost: No valid host was found. There are not enough hosts available.

In compute node /var/log/nova/nova-compute.log shows:

2015-06-22 22:33:33.640 22560 INFO nova.compute.claims [-] [instance: 0f326b28-bef5-4d77-99c8-0949e3a00dbf] Attempting claim: memory 512 MB, disk 1 GB
2015-06-22 22:33:33.640 22560 INFO nova.compute.claims [-] [instance: 0f326b28-bef5-4d77-99c8-0949e3a00dbf] Total memory: 7741 MB, used: 512.00 MB
2015-06-22 22:33:33.640 22560 INFO nova.compute.claims [-] [instance: 0f326b28-bef5-4d77-99c8-0949e3a00dbf] memory limit: 11611.50 MB, free: 11099.50 MB
2015-06-22 22:33:33.641 22560 INFO nova.compute.claims [-] [instance: 0f326b28-bef5-4d77-99c8-0949e3a00dbf] Total disk: 98 GB, used: 0.00 GB
2015-06-22 22:33:33.641 22560 INFO nova.compute.claims [-] [instance: 0f326b28-bef5-4d77-99c8-0949e3a00dbf] disk limit not specified, defaulting to unlimited
2015-06-22 22:33:33.657 22560 INFO nova.compute.claims [-] [instance: 0f326b28-bef5-4d77-99c8-0949e3a00dbf] Claim successful
2015-06-22 22:33:33.736 22560 INFO nova.scheduler.client.report [-] Compute_service record updated for ('node-79', 'node-79')
2015-06-22 22:33:33.911 22560 INFO nova.scheduler.client.report [-] Compute_service record updated for ('node-79', 'node-79')
2015-06-22 22:33:34.089 22560 INFO nova.virt.libvirt.driver [req-ba296006-b580-4e49-ab9e-506f3f3d8d31 - - - - -] [instance: 0f326b28-bef5-4d77-99c8-0949e3a00dbf] Creating image
2015-06-22 22:33:34.277 22560 INFO nova.scheduler.client.report [-] Compute_service record updated for ('node-79', 'node-79')
2015-06-22 22:33:36.754 22560 ERROR nova.compute.manager [req-ba296006-b580-4e49-ab9e-506f3f3d8d31 - - - - -] [instance: 0f326b28-bef5-4d77-99c8-0949e3a00dbf] Instance failed to spawn
2015-06-22 22:33:36.754 22560 TRACE nova.compute.manager [instance: 0f326b28-bef5-4d77-99c8-0949e3a00dbf] Traceback (most recent call last):
2015-06-22 22:33:36.754 22560 TRACE nova.compute.manager [instance: 0f326b28-bef5-4d77-99c8-0949e3a00dbf] File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2442, in _build_resources
2015-06-22 22:33:36.754 22560 TRACE nova.compute.manager [instance: 0f326b28-bef5-4d77-99c8-0949e3a00dbf] yield resources
2015-06-22 22:33:36.754 22560 TRACE nova.compute.manager [instance: 0f326b28-bef5-4d77-99c8-0949e3a00dbf] File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2314, in _build_and_run_instance
2015-06-22 22:33:36.754 22560 TRACE nova.compute.manager [instance: 0f326b28-bef5-4d77-99c8-0949e3a00dbf] block_device_info=block_device_info)
2015-06-22 22:33:36.754 22560 TRACE nova.compute.manager [instance: 0f326b28-bef5-4d77-99c8-0949e3a00dbf] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 2351, in spawn
2015-06-22 22:33:36.754 22560 TRACE nova.compute.manager [instance: 0f326b28-bef5-4d77-99c8-0949e3a00dbf] write_to_disk=True)
2015-06-22 22:33:36.754 22560 TRACE nova.compute.manager [instance: 0f326b28-bef5-4d77-99c8-0949e3a00dbf] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 4172, in _get_guest_xml
2015-06-22 22:33:36.754 22560 TRACE nova.compute.manager [instance: 0f326b28-bef5-4d77-99c8-0949e3a00dbf] context)
2015-06-22 22:33:36.754 22560 TRACE nova.compute.manager [instance: 0f326b28-bef5-4d77-99c8-0949e3a00dbf] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 4043, in _get_guest_config
2015-06-22 22:33:36.754 22560 TRACE nova.compute.manager [instance: 0f326b28-bef5-4d77-99c8-0949e3a00dbf] flavor, virt_type)
2015-06-22 22:33:36.754 22560 TRACE nova.compute.manager [instance: 0f326b28-bef5-4d77-99c8-0949e3a00dbf] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/vif.py", line 374, in get_config
2015-06-22 22:33:36.754 22560 TRACE nova.compute.manager [instance: 0f326b28-bef5-4d77-99c8-0949e3a00dbf] _("Unexpected vif_type=%s") % vif_type)
2015-06-22 22:33:36.754 22560 TRACE nova.compute.manager [instance: 0f326b28-bef5-4d77-99c8-0949e3a00dbf] NovaException: Unexpected vif_type=binding_failed
2015-06-22 22:33:36.754 22560 TRACE nova.compute.manager [instance: 0f326b28-bef5-4d77-99c8-0949e3a00dbf]
2015-06-22 22:33:36.755 22560 INFO nova.compute.manager [req-73d92fcd-e293-4581-b9fe-ec060ed40de6 5e725319a5804879b9db7ee2aad6241d 92272f7c0c9d4cd884037296afdc2d66 - - -] [instance: 0f326b28-bef5-4d77-99c8-0949e3a00dbf] Terminating instance

others log haven't error

elrondwang (elrondwong)
Changed in nova:
assignee: nobody → Moonlight -shadow (1403383953-h)
assignee: Moonlight -shadow (1403383953-h) → nobody
Revision history for this message
Jeremy Stanley (fungi) wrote :

Your description doesn't explain why this was opened as a private security vulnerability report. If this was meant to be a normal bug report, please switch it from "private security" to just "public" so that the nova developers will be able to see it. Thanks!

elrondwang (elrondwong)
information type: Private Security → Public
tags: added: libvirt network
Revision history for this message
Markus Zoeller (markus_z) (mzoeller) wrote :

@Moonlight -shadow (1403383953-h):

The error "Unexpected vif_type=binding_failed" could be caused by a misconfiguration of Neutron. You could try [1] to resolve this. Also the "nova.conf" configuration option "vif_plugging_is_fatal=False" [2] could help you, depending on the purpose of your OpenStack installation. I close this bug as "invalid". Please feel free to set this bug to "new" again if you think that there is an issue which is not caused by a misconfiguration.

[1] https://ask.openstack.org/en/question/48407/instance-failing-to-spawn-logs-show-novaexception-unexpected-vif_typebinding_failed/
[2] http://docs.openstack.org/kilo/config-reference/content/list-of-compute-config-options.html

Changed in nova:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.