Ask Your Question

Instance creation fails - neutron problem

asked 2014-08-04 09:12:22 -0500

hannuvisti gravatar image


I am experimenting with Neutron as I have never managed to get it up and running, by following the openstack labs training guide with Icehouse.

I have a three-node configuration (control, compute, network) in principle up and running but instances fail to launch. Errors in compute node nova-compute.log include

2014-08-04 13:11:02.939 1780 ERROR nova.compute.manager [req-0ec5664e-ce72-47b9-9b10-b79a4ab0ecea e354b8a4b1e8418bbfdc6d4c9bc5a442 566c2813ebe64b0093e6bb7bd24d95e6] [instance: 85ed0798-65d6-4347-adbe-f1b8f167a8da] Instance failed to spawn 
2014-08-04 13:11:03.048 1780 AUDIT nova.compute.manager [req-0ec5664e-ce72-47b9-9b10-b79a4ab0ecea e354b8a4b1e8418bbfdc6d4c9bc5a442 566c2813ebe64b0093e6bb7bd24d95e6] [instance: 85ed0798-65d6-4347-adbe-f1b8f167a8da] Terminating instance 2014-08-04 13:11:03.053 1780 ERROR nova.virt.libvirt.driver [-] [instance: 85ed0798-65d6-4347-adbe-f1b8f167a8da] During wait destroy, instance disappeared. 
2014-08-04 13:11:03.457 1780 ERROR nova.compute.manager [req-0ec5664e-ce72-47b9-9b10-b79a4ab0ecea e354b8a4b1e8418bbfdc6d4c9bc5a442 566c2813ebe64b0093e6bb7bd24d95e6] [instance: 85ed0798-65d6-4347-adbe-f1b8f167a8da] Error: Unexpected vif_type=binding_failed

According to Google this error originates from Neutron, which is plausible as I also get an error when openvswitch-agent starts in compute:

2014-08-04 12:53:17.650 1816 ERROR neutron.agent.linux.ovsdb_monitor [req-b080210a-d8aa-4744-ba1f-a15bc23c27de None] Error received from ovsdb monitor: 2014-08-04T11:53:17Z|00001|fatal_signal|WARN|terminating with signal 15 (Terminated)

Network node does not display any errors nor any kind of activity when trying to launch an instance. Upon neutron start, it logs the following warning:

2014-08-04 12:38:51.141 7358 WARNING neutron.plugins.openvswitch.agent.ovs_neutron_agent [-] Device 5ff42b82-be16-40f6-93c0-cee8e271e357 not defined on plugin

When I issue neutron agent-list, everything appears to be running:

visti@control2:~$ neutron agent-list
| id                                   | agent_type         | host     | alive | admin_state_up |
| 1151fa16-1a80-4cf2-bc48-9df2b9bc4953 | Open vSwitch agent | network2 | :-)   | True           |
| 50286976-cb24-4907-a50c-d59e5bf1ffe5 | DHCP agent         | network2 | :-)   | True           |
| 52e8f4ef-97dc-4a1a-a271-8a106403223a | Open vSwitch agent | compute2 | :-)   | True           |
| 6d4857ed-eaaf-4b9a-9405-c4e87f1b6d97 | L3 agent           | network2 | :-)   | True           |
| a079c7b1-3bf6-469d-8261-13fe122d4fb8 | Metadata agent     | network2 | :-)   | True           |

This appears to be a problem suffered by others as well, but there appears to be very limited info on how to fix this if all the agents are actually running.

edit retag flag offensive close merge delete


Is this setup ML2&OVS&GRE ?

dbaxps gravatar imagedbaxps ( 2014-08-04 10:03:37 -0500 )edit

I assume it is. ( is the guide I am following - more or less. I have gre tunnels defined as well as ovs installed. I have edited ml2 configuration file, too

hannuvisti gravatar imagehannuvisti ( 2014-08-05 05:19:54 -0500 )edit
dbaxps gravatar imagedbaxps ( 2014-08-05 05:43:06 -0500 )edit

2 answers

Sort by ยป oldest newest most voted

answered 2014-08-04 14:33:06 -0500

semyazz gravatar image

Maybe you'll find more in openvswitch's log - /var/log/openvswitchovs-vswitchd.log

I've encountered multiple issues when I was setting up the whole neutron manually. In general if neutron doesn't work nothing works :)


are very helpful and be sure the whole configs are consistent. Once I misspelled one option and couldn't find out why it didn't work.

edit flag offensive delete link more


Openvswitch logs shows the following:

2014-08-05T10:24:54.965Z|00027|bridge|INFO|bridge br-int: added interface tap0bd5655a-01 on port 2 2014-08-05T10:24:55.292Z|00028|netdev_linux|INFO|ioctl(SIOCGIFHWADDR) on tap0bd5655a-01 device failed: No such device

hannuvisti gravatar imagehannuvisti ( 2014-08-05 05:43:00 -0500 )edit

answered 2014-08-27 07:41:17 -0500

Nitish gravatar image

I am adding the logs where I have the same issue. The VM as soon as it is spawned, goes to the ERROR state and the logs say that "vif_type=binding failed". Tried quite a few of the previous answers and nothing seems to work! The logs are available at Let me know how to fix this.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2014-08-04 08:23:30 -0500

Seen: 198 times

Last updated: Aug 04 '14