[one-users] Remove VMs stuck in prolog

[Javier Fontan]

Hello,

If you are using version 1.2 you can use this script to delete stuck
VM's and fix the database afterwards:

http://dev.opennebula.org/projects/scripts/wiki/Onedb

Due to a bug in the ruby API you will also need to update
$ONE_LOCATION/lib/ruby/one.rb with this file:

http://dev.opennebula.org/projects/opennebula/repository/entry/branches/one-1.2/src/client/ruby/one.rb

Use the download link. After that follow the instructions in the onedb
wiki page and it should free that VM's and network leases.

Bye



On Thu, Aug 20, 2009 at 3:36 PM, Sander Klous<sander at nikhef.nl> wrote:
> Hi,
> I am testing some modifications in my transfer scripts. Due to some mistakes
> I made in those scripts, VMs are stuck in prolog state. Is there a way to
> force kill them (without deleting the entire database)? They are eating up
> my IP numbers and polluting my onevm list. If I delete the database I have
> to recreate the network and reassign the nodes.
> Thanks,
> Sander
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>



-- 
Javier Fontan, Grid & Virtualization Technology Engineer/Researcher
DSA Research Group: http://dsa-research.org
Globus GridWay Metascheduler: http://www.GridWay.org
OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org