[one-users] Problem with shared_lvm driver

Carlos Martín Sánchez cmartin at opennebula.org
Mon Apr 8 02:38:21 PDT 2013


Hi,

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.

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.

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.

Regards

--
Carlos Martín, MSc
Project Engineer
OpenNebula - The Open-source Solution for Data Center Virtualization
www.OpenNebula.org | cmartin at opennebula.org |
@OpenNebula<http://twitter.com/opennebula><cmartin at opennebula.org>


On Thu, Apr 4, 2013 at 10:02 AM, Alan Jurcic <alan.jurcic at carnet.hr> wrote:

> Hi,
>
> While testing the shared LVM driver
> (http://wiki.opennebula.org/shared_lvm) I've stumbled upon a slight
> issue while trying to delete a VM with persistent image.
>
> All other combinations of shutdown or delete with non-persistent or
> persistent images work except deleting. The problem seems to be in the
> order the scripts are executing:
>
> Thu Apr  4 09:37:28 2013 [DiM][I]: New VM state is DONE
> Thu Apr  4 09:37:28 2013 [VMM][W]: Ignored: LOG I 1012 Driver command
> for 1012 cancelled
> Thu Apr  4 09:37:28 2013 [TM][W]: Ignored: LOG I 1012 LV vg1/lv-one-317
> in use: not deactivating
> Thu Apr  4 09:37:28 2013 [TM][W]: Ignored: LOG I 1012 ExitCode: 0
> Thu Apr  4 09:37:28 2013 [TM][W]: Ignored: LOG I 1012 delete: Deleting
> /var/lib/one/datastores/0/1012
> Thu Apr  4 09:37:28 2013 [TM][W]: Ignored: LOG I 1012 ExitCode: 0
> Thu Apr  4 09:37:28 2013 [TM][W]: Ignored: TRANSFER SUCCESS 1012 -
> Thu Apr  4 09:37:29 2013 [VMM][W]: Ignored: LOG I 1012 ExitCode: 0
> Thu Apr  4 09:37:29 2013 [VMM][W]: Ignored: LOG I 1012 Successfully
> execute virtualization driver operation: cancel.
> Thu Apr  4 09:37:29 2013 [VMM][W]: Ignored: LOG I 1012 ExitCode: 0
> Thu Apr  4 09:37:29 2013 [VMM][W]: Ignored: LOG I 1012 Successfully
> execute network driver operation: clean.
> Thu Apr  4 09:37:29 2013 [VMM][W]: Ignored: CANCEL SUCCESS 1012 -
>
> Looks like nebula is cleaning up images before destroying the VM which
> is kinda weird. It works with non-persistent images because you can
> force removal of LV, but you can't deactivate it while it's being used.
>
> Is this ordering different in more recent versions of OpenNebula (we're
> using 3.4 atm)? Short of upgrading, are there any simple solutions to
> this that I'm missing?
>
> Regards,
> Alan
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20130408/4eb5605e/attachment-0002.htm>


More information about the Users mailing list