Traceback in nova-compute when attempting to delete an instance that is already destroyed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Triaged
|
Low
|
Unassigned |
Bug Description
The following traceback is output into the nova-compute log when trying to delete an instance that has already been destroyed:
2012-03-19 10:04:51 ERROR nova.rpc.amqp [-] Exception during message handling
(nova.rpc.amqp): TRACE: Traceback (most recent call last):
(nova.rpc.amqp): TRACE: File "/opt/stack/
(nova.rpc.amqp): TRACE: rval = node_func(
(nova.rpc.amqp): TRACE: File "/opt/stack/
(nova.rpc.amqp): TRACE: return f(*args, **kw)
(nova.rpc.amqp): TRACE: File "/opt/stack/
(nova.rpc.amqp): TRACE: function(self, context, instance_uuid, *args, **kwargs)
(nova.rpc.amqp): TRACE: File "/opt/stack/
(nova.rpc.amqp): TRACE: sys.exc_info())
(nova.rpc.amqp): TRACE: File "/usr/lib/
(nova.rpc.amqp): TRACE: self.gen.next()
(nova.rpc.amqp): TRACE: File "/opt/stack/
(nova.rpc.amqp): TRACE: return function(self, context, instance_uuid, *args, **kwargs)
(nova.rpc.amqp): TRACE: File "/opt/stack/
(nova.rpc.amqp): TRACE: self._delete_
(nova.rpc.amqp): TRACE: File "/opt/stack/
(nova.rpc.amqp): TRACE: self._shutdown_
(nova.rpc.amqp): TRACE: File "/opt/stack/
(nova.rpc.amqp): TRACE: raise exception.
(nova.rpc.amqp): TRACE: Invalid: trying to destroy already destroyed instance: ceafeff4-
(nova.rpc.amqp): TRACE:
Typically, I see this when Tempest is running test cases where an instance has gone (correctly or not) into an Error status, with a power_state of Shutoff and task_state of Deleting.
Doesn't look like it is causing usability issues, but an exception definitely sounds like overkill