When Neutron is enabled, an error occurs on network allocation.
2013-11-01 15:41:07.684 ERROR nova.compute.manager [req-c1b6e8a2-e212-4457-97c1-a32bbef4ba33 demo demo] [instance: b3322776-7d43-47a8-8283-7be1415c1fda] Instance failed to spawn
2013-11-01 15:41:07.684 TRACE nova.compute.manager [instance: b3322776-7d43-47a8-8283-7be1415c1fda] Traceback (most recent call last):
2013-11-01 15:41:07.684 TRACE nova.compute.manager [instance: b3322776-7d43-47a8-8283-7be1415c1fda] File "/opt/stack/nova/nova/compute/manager.py", line 1436, in _spawn
2013-11-01 15:41:07.684 TRACE nova.compute.manager [instance: b3322776-7d43-47a8-8283-7be1415c1fda] block_device_info)
2013-11-01 15:41:07.684 TRACE nova.compute.manager [instance: b3322776-7d43-47a8-8283-7be1415c1fda] File "/opt/stack/nova/nova/virt/docker/driver.py", line 317, in spawn
2013-11-01 15:41:07.684 TRACE nova.compute.manager [instance: b3322776-7d43-47a8-8283-7be1415c1fda] instance_id=instance['name'])
2013-11-01 15:41:07.684 TRACE nova.compute.manager [instance: b3322776-7d43-47a8-8283-7be1415c1fda] InstanceDeployFailure: Cannot setup network: Unexpected error while running command.
2013-11-01 15:41:07.684 TRACE nova.compute.manager [instance: b3322776-7d43-47a8-8283-7be1415c1fda] Command: sudo nova-rootwrap /etc/nova/rootwrap.conf brctl addif br-int pvnetl80836
2013-11-01 15:41:07.684 TRACE nova.compute.manager [instance: b3322776-7d43-47a8-8283-7be1415c1fda] Exit code: 1
2013-11-01 15:41:07.684 TRACE nova.compute.manager [instance: b3322776-7d43-47a8-8283-7be1415c1fda] Stdout: ''
2013-11-01 15:41:07.684 TRACE nova.compute.manager [instance: b3322776-7d43-47a8-8283-7be1415c1fda] Stderr: "can't add pvnetl80836 to bridge br-int: Operation not supported\n"
2013-11-01 15:41:07.684 TRACE nova.compute.manager [instance: b3322776-7d43-47a8-8283-7be1415c1fda]
is the scenario here also true when using neutron ml2 plugin + linuxbridge agent? I would've expected linuxbridge agent to work here.
Note -- even when using nova-net (not neutron) i've seen this error on the 1st vm boot... however subsequent boot calls succeed so I suspect the underlying code creates the bridge regardless of the error and the bridge can then be used in subsequent boots.