libvirt error when create VM with 2 NICs under DevStack
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Ryota Mibu | ||
Icehouse |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Under a stock DevStack setup on bare metal, I started stack.sh, which creates a public network (w/o DHCP) and a private network (with DHCP) and a router. On the host I created a br-ex and added eth3 to the bridge. The public network is connected via a physical switch, to another host (also running Devstack).
I am able to create VMs, and ping between them, and I can also (with the new VPNaaS feature under development) ping VMs over the public (provider?) network.
If I create a VM (seen this with cirros and others) and specify the private network, or create a VM with the public network, they launch fine. However, if I try to boot an instance with two NICs, the launch fails:
localnet=`neutron net-list | grep private | cut -f 2 -d'|' | cut -f 2 -d' '`
nova boot --image cirros-
pubnet=`neutron net-list | grep public | cut -f 2 -d'|' | cut -f 2 -d' '`
nova boot --image cirros-
nova boot --image cirros-
nova list
+------
| ID | Name | Status | Task State | Power State | Networks |
+------
| 0fc9c41c-
| 76925e14-
| c8cd45a4-
+------
Looking at the logs, I see that the screen-n-cpu.log reports an error and has a traceback:
2013-09-04 18:01:47.963 ERROR nova.compute.
2013-09-04 18:01:47.963 9855 TRACE nova.compute.
2013-09-04 18:01:47.963 9855 TRACE nova.compute.
2013-09-04 18:01:47.963 9855 TRACE nova.compute.
2013-09-04 18:01:47.963 9855 TRACE nova.compute.
2013-09-04 18:01:47.963 9855 TRACE nova.compute.
2013-09-04 18:01:47.963 9855 TRACE nova.compute.
e_domain_
2013-09-04 18:01:47.963 9855 TRACE nova.compute.
)
2013-09-04 18:01:47.963 9855 TRACE nova.compute.
e_domain
2013-09-04 18:01:47.963 9855 TRACE nova.compute.
2013-09-04 18:01:47.963 9855 TRACE nova.compute.
e_domain
2013-09-04 18:01:47.963 9855 TRACE nova.compute.
2013-09-04 18:01:47.963 9855 TRACE nova.compute.
9, in doit
2013-09-04 18:01:47.963 9855 TRACE nova.compute.
2013-09-04 18:01:47.963 9855 TRACE nova.compute.
9, in proxy_call
2013-09-04 18:01:47.963 9855 TRACE nova.compute.
2013-09-04 18:01:47.963 9855 TRACE nova.compute.
, in tworker
2013-09-04 18:01:47.963 9855 TRACE nova.compute.
2013-09-04 18:01:47.963 9855 TRACE nova.compute.
ithFlags
2013-09-04 18:01:47.963 9855 TRACE nova.compute.
dom=self)
2013-09-04 18:01:47.963 9855 TRACE nova.compute.
variables: DHCPSERVER
There is no DHCP server on the public network, but there is one on the local network.
This is consistently reproducible and occurs with other image types.
The nova code is off the master branch (havana) with the SHA1 of 86c97ff from 6 days ago.
tags: | added: libvirt |
Changed in nova: | |
status: | New → Confirmed |
Changed in nova: | |
importance: | Undecided → Medium |
Changed in nova: | |
status: | Confirmed → Incomplete |
assignee: | nobody → Ryota Mibu (r-mibu) |
tags: | added: icehouse-rc-potential |
tags: |
added: icehouse-backport-potential removed: icehouse-rc-potential |
Changed in nova: | |
milestone: | none → juno-2 |
status: | Fix Committed → Fix Released |
tags: | removed: icehouse-backport-potential |
Changed in nova: | |
milestone: | juno-2 → 2014.2 |
I found the problem in another bug report. See https:/ /bugs.launchpad .net/neutron/ +bug/1186557