nova-compute startup failure on Fedora 19 fresh install (no suitable emulator)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Dan Prince |
Bug Description
Using the latest Nova havana release on Fedora 19. I see the following stack trace in Nova's compute.log file after performing a fresh install of Nova/libvirt/qemu and trying to start nova-compute:
2013-08-22 19:01:57.245 9050 ERROR nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:01:57.245 9050 TRACE nova.openstack.
2013-08-22 19:03:25.960 9155 WARNING nova.virt.
----------------
I've filed a related Bugzilla on the isolated libvirt issue here:
https:/
This is using libvirt 1.0.5.5-1.
A couple of things can be done to work around this error.
1) Manually call 'virsh capabilities' and then restart nova-compute.
2) In the Nova libvirt driver if we reverse the order we call getVersion and getCapabilites it also seems to fix it.
Changed in nova: | |
assignee: | nobody → Dan Prince (dan-prince) |
status: | New → In Progress |
This was fixed in baadaa9842ad4ff 8b637466affd3c9 f2213b55ac.
Updates the Nova libvirt driver so we make a call to get
the driver capabilities. This is clearly a work around
but it does allow nova-compute to startup cleanly when
performing a clean install of Fedora 19.
See notes in: https:/ /bugzilla. redhat. com/show_ bug.cgi? id=1000116
Fixes LP Bug #1215593.
Change-Id: I2c74dc001032e3 cc4d7d55a3fa407 b96fd0d0e78