Open Stack

As Gabe mentions, If your running Folsom, use the `nova reset-state`
command.

Otherwise - On Diablo/Essex, I've used SQL to reset the 3x instance state
columns manually to power_state=1, task_state=NULL, vm_state='active' and
then just used `nova delete` to kill it.

As with the Folsom command, this requires that all services are up and
running, and whatever caused it to fail initially has been resolved.

99% of the time the failures are transient and it will succeed the second
time.

Thanks,
Kiall


On Wed, Sep 19, 2012 at 4:19 AM, Samuel Winchenbach <swinchen at gmail.com>wrote:

> Hi All,
>
>
> I was wondering what the correct way to handle a misbehaving instance
> is?  I have, on several occasions, gotten VM instances stuck in an odd
> state such as reboot, deleting, or active when either KVM failed to
> start, or who knows what.   What is the correct procedure for manually
> removing/repairing a misbehaving VM?
>
> Right now I have been using this SQL script: http://paste2.org/p/2240202
> The problem is, this does not undo all the networking changes, or
> delete the various files in /var/lib/nova/instances and
> /etc/libvirt/...
>
> Is there a better way to handle this situation than completely nuking
> the database?  If not then what do I need to do to undo the changes to
> the network/iptables?
>
> Thanks,
> Sam
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20120919/e81352a0/attachment.html>