Revision history [back]

click to hide/show revision 1
initial version

Instance creation fails - neutron problem

Hi,

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.