OpenNebula

From hakan.isaksson@init.se
-----

after upgrading from vmware-2.98 to vmware-3.0.0 vm-templates that have more than one image no longer works,
because the first image is copied and then erased when the second is copied.

Here is a log:

Wed Dec 7 16:11:21 2011 [DiM][I]: New VM state is ACTIVE.
Wed Dec 7 16:11:21 2011 [LCM][I]: New VM state is PROLOG.
Wed Dec 7 16:11:21 2011 [VM][I]: Virtual Machine has no context
Wed Dec 7 16:13:05 2011 [TM][D]: tm_clone.sh: dev-clm1.init.se:/srv/cloud/one/var/images/6f741b4a8d3d1bce8898777ee74bfa49 dev-clmesx1.init.se:/srv/cloud/one/var//105/images/disk.0
Wed Dec 7 16:13:05 2011 [TM][D]: tm_clone.sh: DST: /srv/cloud/one/var//105/images/disk.0
Wed Dec 7 16:13:05 2011 [TM][I]: tm_clone.sh: Creating directory /srv/cloud/one/var//105/images
Wed Dec 7 16:13:05 2011 [TM][I]: tm_clone.sh: Executed "rm rf /srv/cloud/one/var//105/images".
Wed Dec 7 16:13:05 2011 [TM][I]: tm_clone.sh: Executed "mkdir -p /srv/cloud/one/var//105/images/disk.0".
Wed Dec 7 16:13:05 2011 [TM][I]: tm_clone.sh: Executed "chmod a+w /srv/cloud/one/var//105/images/disk.0".
Wed Dec 7 16:13:05 2011 [TM][I]: tm_clone.sh: Cloning /srv/cloud/one/var/images/6f741b4a8d3d1bce8898777ee74bfa49
Wed Dec 7 16:13:05 2011 [TM][I]: tm_clone.sh: Executed "cp -r /srv/cloud/one/var/images/6f741b4a8d3d1bce8898777ee74bfa49/* /srv/cloud/one/var//105/images/disk.0".
Wed Dec 7 16:13:05 2011 [TM][I]: tm_clone.sh: Executed "chmod a+rw /srv/cloud/one/var//105/images/disk.0".
Wed Dec 7 16:13:05 2011 [TM][I]: ExitCode: 0
Wed Dec 7 16:13:07 2011 [TM][D]: tm_clone.sh: dev-clm1.init.se:/srv/cloud/one/var/images/a14fae29abc5f39fade2ebed13f61646 dev-clmesx1.init.se:/srv/cloud/one/var//105/images/disk.1
Wed Dec 7 16:13:07 2011 [TM][D]: tm_clone.sh: DST: /srv/cloud/one/var//105/images/disk.1
Wed Dec 7 16:13:07 2011 [TM][I]: tm_clone.sh: Creating directory /srv/cloud/one/var//105/images
Wed Dec 7 16:13:07 2011 [TM][I]: tm_clone.sh: Executed "rm -rf /srv/cloud/one/var//105/images".
Wed Dec 7 16:13:07 2011 [TM][I]: tm_clone.sh: Executed "mkdir -p /srv/cloud/one/var//105/images/disk.1".
Wed Dec 7 16:13:07 2011 [TM][I]: tm_clone.sh: Executed "chmod a+w /srv/cloud/one/var//105/images/disk.1".
Wed Dec 7 16:13:07 2011 [TM][I]: tm_clone.sh: Cloning /srv/cloud/one/var/images/a14fae29abc5f39fade2ebed13f61646
Wed Dec 7 16:13:07 2011 [TM][I]: tm_clone.sh: Executed "cp -r /srv/cloud/one/var/images/a14fae29abc5f39fade2ebed13f61646/* /srv/cloud/one/var//105/images/disk.1".
Wed Dec 7 16:13:07 2011 [TM][I]: tm_clone.sh: Executed "chmod a+rw /srv/cloud/one/var//105/images/disk.1".
Wed Dec 7 16:13:07 2011 [TM][I]: ExitCode: 0
Wed Dec 7 16:13:07 2011 [LCM][I]: New VM state is BOOT
Wed Dec 7 16:13:07 2011 [VMM][I]: Generating deployment file: /srv/cloud/one/var/105/deployment.0
-- the boot gets stuck here because the OS-image no longer exist

The line that does "rm -rf /srv/cloud/one/var//105/images" was added in vmware-3.0.0

If I remove the rm line in /srv/cloud/one/lib/tm_commands/vmware/tm_clone.sh
starting the vm works.

I guess the proper way to solve this would be to do "rm -rf /srv/cloud/one/var//105/images/disk.<nr>" instead.

(I'm using opennebula-3.0.0)