openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #06459
Re: openstack nova-comoute boot instance error (diablo)
Pádraig Brady wrote:
> On 12/24/2011 03:47 AM, darkfower wrote:
>> hi,everybody:
>>
>> when i new create a kvm instance , error as flollow:
>>
>>
>> 2011-12-24 11:45:17,937 INFO nova.virt.libvirt_conn [-] Instance instance-00000001 spawned successfully.
>> 2011-12-24 11:45:18,126 ERROR nova.exception [-] DB exception wrapped.
>> (nova.exception): TRACE: Traceback (most recent call last):
>> (nova.exception): TRACE: File "/usr/lib/python2.7/dist-packages/nova/exception.py", line 78, in _wrap
>> (nova.exception): TRACE: return f(*args, **kwargs)
>> (nova.exception): TRACE: File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 1359, in flush
>> (nova.exception): TRACE: self._flush(objects)
>> (nova.exception): TRACE: File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 1447, in _flush
>> (nova.exception): TRACE: raise
>> (nova.exception): TRACE: TypeError: exceptions must be old-style classes or derived from BaseException, not NoneType
>> (nova.exception): TRACE:
>> 2011-12-24 11:45:18,140 WARNING nova.compute.manager [-] Error during power_state sync: exceptions must be old-style classes or derived from BaseException, not NoneType
>
> I've seen this due to greenthread clearing the exception,
> thus None is reraised, rather than the original exception.
> nova.utils.save_and_reraise_exception() was created to avoid this,
> so perhaps there is a missing use of this?
Could you please file a bug (with details like version used) about this
at: https://bugs.launchpad.net/nova/+filebug
Mailing-lists make awful bug trackers.
--
Thierry Carrez (ttx)
Release Manager, OpenStack
References