openstack team mailing list archive

[Mandar Vaze <mandar.vaze@xxxxxxxxxxxx>]

I agree user shouldn’t have to update DB.
There needs to be some periodic cleanup task that “fixes” the vm_state/task_state for “stuck” instances.

-Mandar

From: openstack-bounces+mandar.vaze=vertex.co.in@xxxxxxxxxxxxxxxxxxx [mailto:openstack-bounces+mandar.vaze=vertex.co.in@xxxxxxxxxxxxxxxxxxx] On Behalf Of Guilherme Birk
Sent: Wednesday, March 21, 2012 6:05 PM
To: Openstack Mail List
Subject: Re: [Openstack] Can't delete instances with "error" status.

This is the only option? I've already done that, but it's kind "strange" I update the database row everytime the script identifies a VM with error.
________________________________
Date: Wed, 21 Mar 2012 09:39:03 +0800
Subject: Re: [Openstack] Can't delete instances with "error" status.
From: mwjpiero@xxxxxxxxx<mailto:mwjpiero@xxxxxxxxx>
To: guibirk@xxxxxxxxxxx<mailto:guibirk@xxxxxxxxxxx>
update "instances" table in "nova" db, set the vm_status of  the instance which you want to delete "active" and set the task_status=NULL.
After that, try to use euca-terminate

On Wed, Mar 21, 2012 at 1:24 AM, Guilherme Birk <guibirk@xxxxxxxxxxx<mailto:guibirk@xxxxxxxxxxx>> wrote:
I'm attempting to make a python script that controls all my virtual machines. Sometimes, when the script identifies that exists an instance with status of "error", he creates a new instance and tries to delete the old one with curl commands, but I'm not getting any response and the VM isn't deleted. When I execute euca-terminate instance <i-name> I got nothing too. How I should delete instances with error status ? I didn't found any way using nova-manage too.

_______________________________________________
Mailing list: https://launchpad.net/~openstack<https://launchpad.net/%7Eopenstack>
Post to     : openstack@xxxxxxxxxxxxxxxxxxx<mailto:openstack@xxxxxxxxxxxxxxxxxxx>
Unsubscribe : https://launchpad.net/~openstack<https://launchpad.net/%7Eopenstack>
More help   : https://help.launchpad.net/ListHelp



--
非淡薄无以明志，非宁静无以致远