Bug #1232

tm clone does not work with non registered images

Added by Javi Fontan almost 8 years ago. Updated over 7 years ago.

Status:ClosedStart date:04/12/2012
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Drivers - Auth
Target version:Release 3.6
Resolution: Pull request:
Affected Versions:OpenNebula 3.4

Description

Jordan Pittier on irc:

there might be a bug in var/remotes/tm/shared/clone
i am using git branch 3.4
I don't understant this line :
SRC_PATH="../../${SRC_PATH##"$DS_DIR/"}"
it appears there is a mix between abs and relative path
I keep seing error like this in log : "Thu Apr 12 18:18:52 2012 [TM][E]: clone: Command "cd /home/oneadmin/var/datastores/0/10; cp -r ../..//home/oneadmin/debian-6.0.4-amd64-netinst.iso /home/oneadmin/var/datastores/0/10/disk.0" failed: cp: impossible d'?valuer ? ../..//home/oneadmin/debian-6.0.4-amd64-netinst.iso ?: no file or folder"

Form the error an code it seems that the substitution is only valid for datastore images.

Associated revisions

Revision 5c1d4edb
Added by Ruben S. Montero almost 8 years ago

bug #1232: Only allow Datastore & volatile disks. Remove automatic target generation. Remove unneeded oned.conf attributes

Revision e401b490
Added by Ruben S. Montero almost 8 years ago

bug #1232: Only allow Datastore & volatile disks. Remove automatic target generation. Remove unneeded oned.conf attributes
(cherry picked from commit 5c1d4edb01894e22c0b52073606787880f93625f)

Revision 44af8c66
Added by Ruben S. Montero almost 8 years ago

bug #1232: Set default targets for EC2 API

Revision 991818e5
Added by Ruben S. Montero almost 8 years ago

bug #1232: Set default targets for EC2 API
(cherry picked from commit 44af8c66076411d1728724801915ba122d8fbd2b)

Revision e72f2f44
Added by Javi Fontan over 7 years ago

Revert "bug #1232: Set default targets for EC2 API"

This reverts commit 991818e5b9dd532cc76c7c85e496c0e53fb90935.

Revision dbfeec46
Added by Javi Fontan over 7 years ago

Revert "bug #1232: Only allow Datastore & volatile disks. Remove automatic target generation. Remove unneeded oned.conf attributes"

This reverts commit 5c1d4edb01894e22c0b52073606787880f93625f.

Revision e9e5d954
Added by Carlos Martín over 7 years ago

Revert "bug #1232: Set default targets for EC2 API"

This reverts commit 44af8c66076411d1728724801915ba122d8fbd2b.

Revision f0c1641f
Added by Carlos Martín over 7 years ago

Revert "bug #1232: Only allow Datastore & volatile disks. Remove automatic target generation. Remove unneeded oned.conf attributes"

This reverts commit e401b4900d99104d77c83f80c2a9e48daf668af5.

Revision 7da6c988
Added by Carlos Martín over 7 years ago

Bug #1232: Bring back part of e401b49 : Only allow Datastore & volatile disks.

Revision c71a92d1
Added by Carlos Martín over 7 years ago

Bug #1232: Improve automatic target assignment

Revision ae6df524
Added by Ruben S. Montero over 7 years ago

bug #1232: Work on the target assginment function

Revision d209fbfe
Added by Carlos Martín over 7 years ago

Bug #1232: Remove the constraint to have at least one OS image

Revision 97cf299f
Added by Carlos Martín over 7 years ago

Bug #1232: Remove context/target att. from ec2 template

History

#1 Updated by jordan pittier almost 8 years ago

This issue only arises when instanciating VM direclty, ie without a template

This fails :

echo 'NAME = "MasterDeb6x64"
OS = [boot="hd", arch="x86_64"]
MEMORY = 1024
DISK=[image="cdrom_Deb6x64"]
DISK=[image="Deb6x64"]
NIC = [ NETWORK="LAB LAN" ]
' > lab_deb_vm

onevm create lab_deb_vm

When I instanciate a VM from a template, everything works fine

#2 Updated by Ruben S. Montero almost 8 years ago

Hi this is in fact, not supported in 3.4. DISK attributes are supposed to be using a Datastore. This prevents some security risks, and it streamlines the storage flow. I agree that for some images (e.g. CD's for OS installation) it really comes in handy the use of plain URLs.

Are we breaking your workflow?

I am leaving this issue open for further discussions or/and update the compatibility guide and documentation to clearly state that the use of SOURCE is not supported.

#3 Updated by jordan pittier almost 8 years ago

This is ok, I worked around it.

Just for info, I now use virt-install to install/create a master of a VM. I find the process of creating a brand new VM (aka a VM template) not straightforward in Opennebula. But once it's done, it's all good :) (love the "contextualisation disk", easy but powerful)

#4 Updated by Ruben S. Montero over 7 years ago

  • Target version set to Release 3.6

#5 Updated by Ruben S. Montero over 7 years ago

  • Status changed from New to Closed

Ok. Now the OpenNebula core will check for this and will not let use non-registered images.

BTW, There have been a couple of messages about people having troubles with the virt-install method. If you want to share your notes we can add it to the wiki or make a blog post. Just drop me a line.

Thanks for the feedback!

Also available in: Atom PDF