You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Kiran Koneti (JIRA)" <ji...@apache.org> on 2013/07/29 13:09:49 UTC
[jira] [Reopened] (CLOUDSTACK-2064) The Vmware template dosent have
permissions to be copied from secondary storage.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kiran Koneti reopened CLOUDSTACK-2064:
--------------------------------------
Re opening this as we still see the issue and was also observed in the customer environment.
> The Vmware template dosent have permissions to be copied from secondary storage.
> --------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2064
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2064
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Install and Setup
> Affects Versions: 4.1.0, 4.2.0
> Reporter: Kiran Koneti
> Assignee: Hugo Trippaers
> Priority: Critical
> Fix For: 4.1.0, 4.2.0
>
>
> When the VMware template is seeded to the secondary storage and while trying to create the system Vm's there is a error message saying no permission to tar the routing-8.ova
> The error message is as below.
> "2013-04-17 11:33:18,074 ERROR [vmware.manager.VmwareStorageManagerImpl] (DirectAgent-4:10.102.192.18) Unable to execute PrimaryStorageDownloadCommand due to exception
> java.io.FileNotFoundException: /var/cloudstack/mnt/VM/222273143235720.4a5f0cef/template/tmpl/1/8/systemvmtemplate-2013-04-15-master-vmware.ovf (Permission denied)
>
> [root@rhel63 management]# ll /var/cloudstack/mnt/VM/
> total 20
> drwxrwxrwx. 2 cloud cloud 4096 Apr 17 10:34 222273143235720.154199bd
> drwxrwxrwx. 5 root bin 4096 Apr 17 11:35 222273143235720.4a5f0cef
> drwxrwxrwx. 2 cloud cloud 4096 Apr 16 11:29 222273143235720.4c8848c4
> drwxrwxrwx. 2 cloud cloud 4096 Apr 16 11:54 222273143235720.525f3d5f
> drwxrwxrwx. 2 cloud cloud 4096 Apr 17 10:44 222273143235720.526d73ac
> [root@rhel63 management]# ll /var/cloudstack/mnt/VM/222273143235720.4a5f0cef/
> drwxrwxr-x. 2 cloud cloud 4096 Apr 17 11:35 systemvm
> drwxr-xr-x. 3 root root 4096 Apr 17 09:41 template
> [root@rhel63 management]# ll /var/cloudstack/mnt/VM/222273143235720.4a5f0cef/template/
> drwxr-xr-x. 3 root root 4096 Apr 17 09:41 tmpl
> -rw-r--r--. 1 root root 260070912 Apr 17 09:56 56058ae3-12ea-4bbc-838c-f2e25ceba314.ova
> -rw-------. 1 root root 260057600 Apr 16 09:49 systemvmtemplate-2013-04-15-master-vmware-disk1.vmdk
> -rw-------. 1 root root 12178 Apr 16 09:49 systemvmtemplate-2013-04-15-master-vmware.ovf
> -rw-r--r--. 1 root root 283 Apr 17 10:00 template.properties"
> There is a workaround for the same.
> After seeding the template if we change the permissions of the template in the secondary storage (i.e give read/write permission) then the template is seeded properly.
--
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