Traceback in nova-compute when attempting to delete an instance that is already destroyed

Bug #959310 reported by Jay Pipes
6
This bug affects 1 person
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/nova/rpc/amqp.py", line 252, in _process_data
(nova.rpc.amqp): TRACE: rval = node_func(context=ctxt, **node_args)
(nova.rpc.amqp): TRACE: File "/opt/stack/nova/nova/exception.py", line 114, in wrapped
(nova.rpc.amqp): TRACE: return f(*args, **kw)
(nova.rpc.amqp): TRACE: File "/opt/stack/nova/nova/compute/manager.py", line 153, in decorated_function
(nova.rpc.amqp): TRACE: function(self, context, instance_uuid, *args, **kwargs)
(nova.rpc.amqp): TRACE: File "/opt/stack/nova/nova/compute/manager.py", line 177, in decorated_function
(nova.rpc.amqp): TRACE: sys.exc_info())
(nova.rpc.amqp): TRACE: File "/usr/lib/python2.7/contextlib.py", line 24, in __exit__
(nova.rpc.amqp): TRACE: self.gen.next()
(nova.rpc.amqp): TRACE: File "/opt/stack/nova/nova/compute/manager.py", line 171, in decorated_function
(nova.rpc.amqp): TRACE: return function(self, context, instance_uuid, *args, **kwargs)
(nova.rpc.amqp): TRACE: File "/opt/stack/nova/nova/compute/manager.py", line 739, in terminate_instance
(nova.rpc.amqp): TRACE: self._delete_instance(context, instance)
(nova.rpc.amqp): TRACE: File "/opt/stack/nova/nova/compute/manager.py", line 719, in _delete_instance
(nova.rpc.amqp): TRACE: self._shutdown_instance(context, instance, 'Terminating')
(nova.rpc.amqp): TRACE: File "/opt/stack/nova/nova/compute/manager.py", line 681, in _shutdown_instance
(nova.rpc.amqp): TRACE: raise exception.Invalid(_msg % instance_uuid)
(nova.rpc.amqp): TRACE: Invalid: trying to destroy already destroyed instance: ceafeff4-110f-4d17-8152-9b7d9e269736
(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.

Revision history for this message
Vish Ishaya (vishvananda) wrote :

Doesn't look like it is causing usability issues, but an exception definitely sounds like overkill

Changed in nova:
status: New → Triaged
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.