[one-users] Recover from FAILED

[Ruben S. Montero]

Hi

Yes there are plans to modify this behavior.

1.- Transitions from UNKNOWN can be improved by not moving automatically
the VMs to FAILED. This way you can issue the boot command, fix anything
and let opennebula rediscover the VM... If the VM cannot be recovered you
may need to delete it (basically the only thing you can do rightnow).

2.- There are plans also to keep the VMs defined and only let them go to
DONE when the user explicitly deletes them. This will happen for OpenNebula
4.0

3.- Right now, you can use "resubmit"

Cheers

Ruben

On Tue, Sep 25, 2012 at 8:40 PM, Ricardo Duarte <rjtd21 at hotmail.com> wrote:

> Hi,
>
> Is there any plan to allow recovery from a failed state?
> Some times that state is not really final. Like, if you have a transient
> error when restarting a VM.
> So, say you got a machine into UNKNOWN state due to some crash on a host.
> You try to restart the VM but there is some error (fixable) that prevents
> the machine from starting. The machine gets into FAILED. You fix the error,
> but can no longer get the machine RUNNING on OpenNebula.
> Currently, that machine is gone even if were able to start it directly
> with virsh.
>
> Regards,
> Ricardo
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
> --
> Ruben S. Montero, PhD
> Project co-Lead and Chief Architect
> OpenNebula - The Open Source Solution for Data Center Virtualization
> <http://lists.opennebula.org/listinfo.cgi/users-opennebula.org>
> www.OpenNebula.org | rsmontero at opennebula.org | @OpenNebula
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20120928/3bb8bdfa/attachment-0002.htm>