Nova fails to start if --start_guests_on_host_boot=true is set
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Dan Prince | ||
Essex |
Fix Released
|
Medium
|
Vish Ishaya |
Bug Description
Whith the following flags set on nova conf:
--start_
--resume_
When a compute node is hard rebooted (or in my case, suffer a power failure), nova-compute is unable to start on the node with the following error:
2012-06-09 11:24:16 INFO nova.virt.
2012-06-09 11:24:17 CRITICAL nova [-] Cannot get interface MTU on 'br100': No such device
2012-06-09 11:24:17 TRACE nova Traceback (most recent call last):
2012-06-09 11:24:17 TRACE nova File "/usr/bin/
2012-06-09 11:24:17 TRACE nova service.wait()
2012-06-09 11:24:17 TRACE nova File "/usr/lib/
2012-06-09 11:24:17 TRACE nova _launcher.wait()
2012-06-09 11:24:17 TRACE nova File "/usr/lib/
2012-06-09 11:24:17 TRACE nova service.wait()
2012-06-09 11:24:17 TRACE nova File "/usr/lib/
2012-06-09 11:24:17 TRACE nova return self._exit_
2012-06-09 11:24:17 TRACE nova File "/usr/lib/
2012-06-09 11:24:17 TRACE nova return hubs.get_
2012-06-09 11:24:17 TRACE nova File "/usr/lib/
2012-06-09 11:24:17 TRACE nova return self.greenlet.
2012-06-09 11:24:17 TRACE nova File "/usr/lib/
2012-06-09 11:24:17 TRACE nova result = function(*args, **kwargs)
2012-06-09 11:24:17 TRACE nova File "/usr/lib/
2012-06-09 11:24:17 TRACE nova server.start()
2012-06-09 11:24:17 TRACE nova File "/usr/lib/
2012-06-09 11:24:17 TRACE nova self.manager.
2012-06-09 11:24:17 TRACE nova File "/usr/lib/
2012-06-09 11:24:17 TRACE nova self.reboot_
2012-06-09 11:24:17 TRACE nova File "/usr/lib/
2012-06-09 11:24:17 TRACE nova return f(*args, **kw)
2012-06-09 11:24:17 TRACE nova File "/usr/lib/
2012-06-09 11:24:17 TRACE nova function(self, context, instance_uuid, *args, **kwargs)
2012-06-09 11:24:17 TRACE nova File "/usr/lib/
2012-06-09 11:24:17 TRACE nova sys.exc_info())
2012-06-09 11:24:17 TRACE nova File "/usr/lib/
2012-06-09 11:24:17 TRACE nova self.gen.next()
2012-06-09 11:24:17 TRACE nova File "/usr/lib/
2012-06-09 11:24:17 TRACE nova return function(self, context, instance_uuid, *args, **kwargs)
2012-06-09 11:24:17 TRACE nova File "/usr/lib/
2012-06-09 11:24:17 TRACE nova reboot_type)
2012-06-09 11:24:17 TRACE nova File "/usr/lib/
2012-06-09 11:24:17 TRACE nova return f(*args, **kw)
2012-06-09 11:24:17 TRACE nova File "/usr/lib/
2012-06-09 11:24:17 TRACE nova if self._soft_
2012-06-09 11:24:17 TRACE nova File "/usr/lib/
2012-06-09 11:24:17 TRACE nova dom.create()
2012-06-09 11:24:17 TRACE nova File "/usr/lib/
2012-06-09 11:24:17 TRACE nova if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
2012-06-09 11:24:17 TRACE nova libvirtError: Cannot get interface MTU on 'br100': No such device
It seems that nova-compute doesn't create the bridge and thus fails to start. Removing both settings from nova conf makes nova-compute start again.
Changed in nova: | |
milestone: | none → folsom-2 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | folsom-2 → 2012.2 |
This was recently changed in trunk. I think this is fixed now.