Unable to delete instance form dashboard

I've found out that there is a problem with rpc.call which should run delete method.

StackTrace:
ERROR nova.openstack.common.rpc.common [-] ['Traceback (most recent call last):\n', ' File "/opt/stack/nova/nova/openstack/common/rpc/amqp.py", line 275, in _process_data\n rval = self.proxy.dispatch(ctxt, version, method, **args)\n', ' File "/opt/stack/nova/nova/openstack/common/rpc/dispatcher.py", line 145, in dispatch\n return getattr(proxyobj, method)(ctxt, **kwargs)\n', ' File "/opt/stack/nova/nova/network/manager.py", line 262, in wrapped\n return func(self, context, *args, **kwargs)\n', ' File "/opt/stack/nova/nova/network/manager.py", line 387, in deallocate_for_instance\n super(FloatingIP, self).deallocate_for_instance(context, **kwargs)\n', ' File "/opt/stack/nova/nova/network/manager.py", line 262, in wrapped\n return func(self, context, *args, **kwargs)\n', ' File "/opt/stack/nova/nova/network/manager.py", line 1003, in deallocate_for_instance\n self.deallocate_fixed_ip(context, fixed_ip[\'address\'])\n', ' File "/opt/stack/nova/nova/network/manager.py", line 248, in deallocate_fixed_ip\n \'args\': args})\n', ' File "/opt/stack/nova/nova/openstack/common/rpc/__init__.py", line 102, in call\n return _get_impl().call(cfg.CONF, context, topic, msg, timeout)\n', ' File "/opt/stack/nova/nova/openstack/common/rpc/impl_kombu.py", line 712, in call\n rpc_amqp.get_connection_pool(conf, Connection))\n', ' File "/opt/stack/nova/nova/openstack/common/rpc/amqp.py", line 368, in call\n rv = list(rv)\n', ' File "/opt/stack/nova/nova/openstack/common/rpc/amqp.py", line 329, in __iter__\n self.done()\n', ' File "/usr/lib/python2.7/contextlib.py", line 24, in __exit__\n self.gen.next()\n', ' File "/opt/stack/nova/nova/openstack/common/rpc/amqp.py", line 326, in __iter__\n self._iterator.next()\n', ' File "/opt/stack/nova/nova/openstack/common/rpc/impl_kombu.py", line 595, in iterconsume\n yield self.ensure(_error_callback, _consume)\n', ' File "/opt/stack/nova/nova/openstack/common/rpc/impl_kombu.py", line 526, in ensure\n error_callbac

here is error which I've found in syslog. I saw also information about amqp timeout. Why rabbit isn't working properly? I can see services on multiple nodes, so rabbit should works, but while I'm "deleting/terminating" instance I see timeout and this stacktrace...

full log from syslog http://pastebin.com/Ww7gfhcZ

maybe now it's more readable. http://paste.openstack.org/show/20599/

This isn't a dashboard bug. The API call happens 100% correctly. There are definitely issues around what happens when services time out, etc. but it's not within Horizon's current purview.

I don't know if there is enough information here to debug the issue. It looks like one of the network hosts is down and therefore the deallocate call is failing.

Can you still reproduce that ? Looks like a one-time error...

As far as I remember it's fixed right now. In October, when I installed
fresh Openstack everything was fine. I forgot about this bug report --
sorry :)

On Thu, Dec 13, 2012 at 11:57 AM, Thierry Carrez <
<email address hidden>> wrote:

> Can you still reproduce that ? Looks like a one-time error...
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1044298
>
> Title:
> Unable to delete instance form dashboard
>
> Status in OpenStack Dashboard (Horizon):
> Won't Fix
> Status in OpenStack Compute (Nova):
> Incomplete
>
> Bug description:
> 4x Ubuntu 12.04. Openstack installed from devstack with cinder.
>
> Creating virtual machines works well, but I can't delete machines.
> Sometimes it works, but almost every time when I'll select more than
> one machine and press "Terminate" it hangs. Status is changed to
> "Deleting", there is log message "Going to try to terminate instance
> from...", but after a while instances are back to "Active" state
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/horizon/+bug/1044298/+subscriptions
>

--
*Semy*

This bug lacks the necessary information to effectively reproduce and fix it, therefore it has been closed. Feel free to reopen the bug by providing the requested information and set the bug status back to ''New''.