Ask Your Question
0

Unable to Launch Instance - Fresh Install 3 Node Openstack - NovaException: Unexpected vif_type=binding_failed

asked 2015-06-27 10:45:18 -0500

flipside786 gravatar image

updated 2015-06-29 07:05:25 -0500

Ranjit gravatar image

Hi Everybody,

I followed the Openstack Installation for Kilo and am attempting to launch my first instance using the Cirros Image. I am getting an Error: No valid host was found. There are not enough hosts available. And in my nova-compute.log on my compute node I am getting the NovaException: Unexpected vif_type=binding_failed.

From reading the other questions of this type of nature it appears it is neutron related. I have checked my ml2 plugin connectivity and deleted and re-added the bridge connections and still no luck. I have pasted the error log below.

Any help is appreciated.

2015-06-27 08:14:32.484 3289 INFO nova.compute.claims [-] [instance: 474c6eee-dee3-416b-95ec-9fa86deeebf6] Total memory: 3939 MB, used: 512.00 MB
2015-06-27 08:14:32.484 3289 INFO nova.compute.claims [-] [instance: 474c6eee-dee3-416b-95ec-9fa86deeebf6] memory limit: 5908.50 MB, free: 5396.50 MB
2015-06-27 08:14:32.491 3289 INFO nova.compute.claims [-] [instance: 474c6eee-dee3-416b-95ec-9fa86deeebf6] Total disk: 97 GB, used: 0.00 GB
2015-06-27 08:14:32.495 3289 INFO nova.compute.claims [-] [instance: 474c6eee-dee3-416b-95ec-9fa86deeebf6] disk limit not specified, defaulting to unlimited
2015-06-27 08:14:32.552 3289 INFO nova.compute.claims [-] [instance: 474c6eee-dee3-416b-95ec-9fa86deeebf6] Claim successful
2015-06-27 08:14:32.750 3289 INFO nova.scheduler.client.report [-] Compute_service record updated for ('compute1', 'compute1')
2015-06-27 08:14:33.092 3289 INFO nova.scheduler.client.report [-] Compute_service record updated for ('compute1', 'compute1')
2015-06-27 08:14:33.968 3289 INFO nova.virt.libvirt.driver [req-ab2b932e-0b9c-427e-93fc-0343eec2d4e2 - - - - -] [instance: 474c6eee-dee3-416b-95ec-9fa86deeebf6] Creating image
2015-06-27 08:14:34.301 3289 INFO nova.scheduler.client.report [-] Compute_service record updated for ('compute1', 'compute1')
2015-06-27 08:14:34.636 3289 INFO nova.virt.disk.vfs.api [req-ab2b932e-0b9c-427e-93fc-0343eec2d4e2 - - - - -] Unable to import guestfs, falling back to VFSLocalFS
2015-06-27 08:14:35.595 3289 ERROR nova.compute.manager [req-ab2b932e-0b9c-427e-93fc-0343eec2d4e2 - - - - -] [instance: 474c6eee-dee3-416b-95ec-9fa86deeebf6] Instance failed to spawn
2015-06-27 08:14:35.595 3289 TRACE nova.compute.manager [instance: 474c6eee-dee3-416b-95ec-9fa86deeebf6] Traceback (most recent call last):
2015-06-27 08:14:35.595 3289 TRACE nova.compute.manager [instance: 474c6eee-dee3-416b-95ec-9fa86deeebf6]   File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2442, in _build_resources
2015-06-27 08:14:35.595 3289 TRACE nova.compute.manager [instance: 474c6eee-dee3-416b-95ec-9fa86deeebf6]     yield resources
2015-06-27 08:14:35.595 3289 TRACE nova.compute.manager [instance: 474c6eee-dee3-416b-95ec-9fa86deeebf6]   File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2314, in _build_and_run_instance
2015-06-27 08:14:35.595 3289 TRACE nova.compute.manager [instance: 474c6eee-dee3-416b-95ec-9fa86deeebf6]     block_device_info=block_device_info)
2015-06-27 08:14:35.595 3289 TRACE nova.compute.manager [instance: 474c6eee-dee3-416b-95ec-9fa86deeebf6]   File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2351, in spawn
2015-06-27 08:14:35.595 3289 TRACE nova.compute.manager [instance: 474c6eee-dee3-416b-95ec-9fa86deeebf6]     write_to_disk=True)
2015-06-27 08:14:35.595 3289 TRACE nova.compute.manager [instance: 474c6eee-dee3-416b-95ec-9fa86deeebf6]   File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 4172, in _get_guest_xml
2015-06-27 08:14:35.595 3289 TRACE nova.compute.manager [instance: 474c6eee-dee3-416b-95ec-9fa86deeebf6]     context)
2015-06-27 08:14:35.595 3289 TRACE nova.compute.manager [instance: 474c6eee-dee3-416b-95ec-9fa86deeebf6]   File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line ...
(more)
edit retag flag offensive close merge delete

Comments

what is the error in neutron logs. Upload it. upload the neutron related conf also. (neutron.conf, ml2 conf files)

Ranjit gravatar imageRanjit ( 2015-06-29 07:09:27 -0500 )edit

Here is the error in the neutron log.

2015-07-02 20:17:22.068 1968 ERROR neutron.plugins.ml2.managers [req-e6c13c01-07ae-4e4e-a833-1ceb85876135 ] Failed to bind port 4214c566-34ad-4eba-9d3a-c5fac806953f on host compute1

flipside786 gravatar imageflipside786 ( 2015-07-02 22:39:55 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2015-07-03 12:30:55 -0500

flipside786 gravatar image

OMG!!!!

I cleaned up my configuration files and removed all the comments from the conf/ini files so I could compare the differences.

in my neutron.conf file I had a random line that started with "%" and I guess it was causing an issue with neutron authentication. In any case, once I removed the line and rebooted all nodes I was good to go.

Thanks Ranjit for providing support on this.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2015-06-27 10:45:18 -0500

Seen: 544 times

Last updated: Jul 03 '15