[one-users] an error associated with onevm delete of persistent image

[Hyun Woo Kim]

Hi Ruben,

Thanks very much for the response.

Fortunately, this does not seem to happen frequently in our cluster
and even if it happens, it does not cause any big trouble,
we just have to manually do "oneimage enable" the persistent image
which went to "err" because of "onevm delete" .

Thanks for confirming this.

HyunWoo


From: "Ruben S. Montero" <rsmontero at opennebula.org<mailto:rsmontero at opennebula.org>>
Date: Wednesday, May 1, 2013 2:58 PM
To: Hyunwoo Kim <hyunwoo at fnal.gov<mailto:hyunwoo at fnal.gov>>
Cc: "users at lists.opennebula.org<mailto:users at lists.opennebula.org>" <users at lists.opennebula.org<mailto:users at lists.opennebula.org>>
Subject: Re: [one-users] an error associated with onevm delete of persistent image

Hi Hyunwoo

Yes totally right, this is in fact a bug that has been solved in recent versions of OpenNebula... In this situation, the delete operation will leave the persistent images in the error state so the consistency of the image can be checked. OpenNebula will not try to move the image back to the datastore. oneimage enable will activate the image again.


Cheers

Ruben




On Wed, May 1, 2013 at 6:43 PM, Hyun Woo Kim <hyunwoo at fnal.gov<mailto:hyunwoo at fnal.gov>> wrote:
Hi,

Let me describe an error situation that I experienced.

We are using ONe3.2.

I launch a VM off a persistent image but it fails at an very early stage (for example tm_ln.sh)
so I end up having a VM in "failed" state.

Next, when I try to delete it via "onevm delete", I have error messages that say
 Message received: LOG E 4 mv: Command "mv -f $ONE_LOCATION/var/56/disk.0 $IRP/images/837d6675a4846f2df76ebbf69d174229" failed.
 Message received: LOG E 4 mv: mv: cannot stat `$ONE_LOCATION/var/56/disk.0': No such file or directory

These error messages make sense because, the launching process failed before doing anything,
thus all of the followings
 - $VM_DIR/images/disk.0
 - $ONE_LOCATION/var/vmid/disk.0
must be absent.

I think what is wrong is,
"onevm delete" on a failed vm from persistent image trying to move disk.0 to the repository.
In other words, "delete" might not be a right operation in this "failed" state for persistent image.
I could not find a right one at least from current list of possible operations for "onevm" command

What will be the right one?

Thank you very much.

Hyunwoo KIM
FermiCloud Project.



_______________________________________________
Users mailing list
Users at lists.opennebula.org<mailto: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
www.OpenNebula.org<http://www.OpenNebula.org> | rsmontero at opennebula.org<mailto:rsmontero at opennebula.org> | @OpenNebula
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20130501/d14b8aa8/attachment-0002.htm>