You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Leeno (JIRA)" <ji...@apache.org> on 2013/06/01 13:30:21 UTC

[jira] [Created] (CLOUDSTACK-2795) Create template failed

Leeno created CLOUDSTACK-2795:
---------------------------------

             Summary: Create template failed
                 Key: CLOUDSTACK-2795
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2795
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: XenServer
    Affects Versions: 4.0.2
         Environment: CS 4.0.2 on Ubuntu 12.04. 
Xenserver 6.0.2
            Reporter: Leeno


Unable to create VM template from snapshots after upgrading to Xenserver 6.0.2 from 6.0.0. But still template feature works with old VMs, ie, VMs created before upgrading to new version.

For new VMs there's a new directory created under the snapshot mount (Eg. /SEC_STORAGE/snapshots/2/1269) with SR name and snapshots are created under it.

root@cstagcms:/cstagzb-sds01/snapshots/2/1269# ls -l
drwxr-xr-x 2 root root 4096 Jun  1 05:36 6585433e-3647-9952-eeba-9823a3d5df08

root@cstagcms:/cstagzb-sds01/snapshots/2/1269# ls -l 6585433e-3647-9952-eeba-9823a3d5df08
total 815608
-rw-r--r-- 1 root root 945603072 Jun  1 05:41 d8bcd1f4-bea0-4263-b3a2-ffe3c94c44e9.vhd


It's not like this for old VMs. There are no SR directories created under snapshot folder. For old VMs,

root@cstagcms:/cstagzb-sds01/snapshots/2/1136# ls -l
total 1262968
-rw-r--r-- 1 root root 1765089792 May 22 09:48 a41ede30-a67e-4256-97a8-c4dafd7094d4.vhd
-rw-r--r-- 1 root root  109388288 May 22 09:52 d726a46e-4fb0-4325-bfab-61a7ac6b20fa.vhd


While creating template, for both new and old VMs, the [vhd file in secondary storage] argument passed to /opt/xensource/bin/create_privatetemplate_from_snapshot.sh script is one with out SR name in path. In that case the script will not find the snapshot for new VMs. I guess, this is the reason for failed template creation.

Is this a known issue or I did something wrong? Can some one help me please.

Thanks in advance.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira