Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Can boot with --availability-zone however if I let Openstack schedule a VM, it will fail with "Unexpected vif_type=binding_failed"

The title says it all. All of the sudden, I haven't been able to schedule any VMs. They all fail with the following error in nova-conductor.log:

2015-07-20 15:17:42.280 71944 WARNING nova.scheduler.driver [req-bc5960d9-15cf-48f4-bace-a58fb057453c None] [instance: b97f7139-016c-4afd-a923-345827a67e63] NoValidHost exception with message: 'No valid host was found. Exceeded max scheduling attempts 3 for instance b97f7139-016c-4afd-a923-345827a67e63. Last exception: [u'Traceback (most recent call last):\n', u'  File "/usr/lib/python2.7/site-packages/nova/compute/", line 2033, in _do_build_and_run_instance\n    filter_properties)\n', u'  File "/usr/lib/python2.7/site-packages/nova/compute/", line 2164, in _build_and_run_instance\n    instance_uuid=instance.uuid, reason=six.text_type(e))\n', u'RescheduledException: Build of instance b97f7139-016c-4afd-a923-345827a67e63 was re-scheduled: Unexpected vif_type=binding_failed\n']'

There haven't been any changes to my configuration files and I've tried various things like restarting the rabbitmq and the mariadb. I also restarted all services on the controller and neutron node. The weird thing about all of this, is that if if use --availability-zone and place the VM directly on a speciffic host, the VM gets booted and has no issues. For example:

nova boot --flavor=m1.small --image=base.img --key-name=login --availability-zone nova:r5b-15 test

Just to be clear, this used to work just fine before. Any help would be greatly appreciated.