Well for posterity or so people can tell me what I did wrong here's
how I seemed to convince the database that the instance was really
deleted:
UPDATE instances SET
vm_state='deleted',task_state='deleted',deleted=1,deleted_at=now()
WHERE uuid=<FOO>
And here's what I had to do to the volume:
UPDATE volumes SET
attach_status='detached',instance_id=NULL,mountpoint=NULL,status='available'
WHERE id=<FOO>
Any insight into how I might determine what when wrong here (essex on
ubuntu 12.04 rabbitmq mysql) or if I missed any pieces that will bite
me are appreciated.
-Jon
On Mon, Jul 30, 2012 at 1:03 PM, Jonathan Proulx <j...@jonproulx.com> wrote:
> Hi All,
>
> I have an instance that has been in this state for a couple days:
>
> | OS-EXT-STS:power_state | 0 |
> | OS-EXT-STS:task_state | deleting |
> | OS-EXT-STS:vm_state | error
> |
>
> with this fault:
>
> | fault | {u'message': u'ProcessExecutionError', u'code': 500,
> u'created': u'2012-07-30T16:51:34Z'} |
>
> sending more delete requests seem to have no effect and the node it
> thinks it is on doesn't seem to have any state about it.
>
> How to I clean this up, do I just need to muck out the DB and if so
> what parts of it?
>
> Thanks,
> -Jon
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
