<div dir="ltr">Hi,<div><br></div><div style>When the VM is running, onevm delete and onevm cancel perform the same driver operations, but with cancel OpenNebula waits for the VMM driver success before deleting the disks.</div>
<div style><br></div><div style>onevm delete is more like a last resort to remove the VM from OpenNebula in case of error. The VM is removed immediately and OpenNebula tries to clean up, but the right way to destroy a VM is onevm cancel.</div>
<div style><br></div><div style>In 4.0 we have synchronized the onevm delete driver operations, but the VM is still removed immediately and if the cleanup fails it is not checked.</div><div style><br></div><div style>Regards</div>
</div><div class="gmail_extra"><br clear="all"><div>--<br>Carlos Martín, MSc<br>Project Engineer<br>OpenNebula - The Open-source Solution for Data Center Virtualization<div><span style="border-collapse:collapse;color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px"><a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:cmartin@opennebula.org" target="_blank">cmartin@opennebula.org</a> | <a href="http://twitter.com/opennebula" target="_blank">@OpenNebula</a></span><span style="border-collapse:collapse;color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px"><a href="mailto:cmartin@opennebula.org" style="color:rgb(42,93,176)" target="_blank"></a></span></div>
</div>
<br><br><div class="gmail_quote">On Thu, Apr 4, 2013 at 10:02 AM, Alan Jurcic <span dir="ltr"><<a href="mailto:alan.jurcic@carnet.hr" target="_blank">alan.jurcic@carnet.hr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
While testing the shared LVM driver<br>
(<a href="http://wiki.opennebula.org/shared_lvm" target="_blank">http://wiki.opennebula.org/shared_lvm</a>) I've stumbled upon a slight<br>
issue while trying to delete a VM with persistent image.<br>
<br>
All other combinations of shutdown or delete with non-persistent or<br>
persistent images work except deleting. The problem seems to be in the<br>
order the scripts are executing:<br>
<br>
Thu Apr 4 09:37:28 2013 [DiM][I]: New VM state is DONE<br>
Thu Apr 4 09:37:28 2013 [VMM][W]: Ignored: LOG I 1012 Driver command<br>
for 1012 cancelled<br>
Thu Apr 4 09:37:28 2013 [TM][W]: Ignored: LOG I 1012 LV vg1/lv-one-317<br>
in use: not deactivating<br>
Thu Apr 4 09:37:28 2013 [TM][W]: Ignored: LOG I 1012 ExitCode: 0<br>
Thu Apr 4 09:37:28 2013 [TM][W]: Ignored: LOG I 1012 delete: Deleting<br>
/var/lib/one/datastores/0/1012<br>
Thu Apr 4 09:37:28 2013 [TM][W]: Ignored: LOG I 1012 ExitCode: 0<br>
Thu Apr 4 09:37:28 2013 [TM][W]: Ignored: TRANSFER SUCCESS 1012 -<br>
Thu Apr 4 09:37:29 2013 [VMM][W]: Ignored: LOG I 1012 ExitCode: 0<br>
Thu Apr 4 09:37:29 2013 [VMM][W]: Ignored: LOG I 1012 Successfully<br>
execute virtualization driver operation: cancel.<br>
Thu Apr 4 09:37:29 2013 [VMM][W]: Ignored: LOG I 1012 ExitCode: 0<br>
Thu Apr 4 09:37:29 2013 [VMM][W]: Ignored: LOG I 1012 Successfully<br>
execute network driver operation: clean.<br>
Thu Apr 4 09:37:29 2013 [VMM][W]: Ignored: CANCEL SUCCESS 1012 -<br>
<br>
Looks like nebula is cleaning up images before destroying the VM which<br>
is kinda weird. It works with non-persistent images because you can<br>
force removal of LV, but you can't deactivate it while it's being used.<br>
<br>
Is this ordering different in more recent versions of OpenNebula (we're<br>
using 3.4 atm)? Short of upgrading, are there any simple solutions to<br>
this that I'm missing?<br>
<br>
Regards,<br>
Alan<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
</blockquote></div><br></div>