[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13464701#comment-13464701
 ] 

Rohit Yadav commented on CLOUDSTACK-223:
----------------------------------------

vmware-base and plugin-vmware should go in to agent? Right now, they go only 
into the server package. This needs checking and may be cause of this issue.
                
> Templates other than SystemVM template are not getting downloaded on Rhel 6.3 
> on a vmware setup with non-oss build
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-223
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-223
>             Project: CloudStack
>          Issue Type: Bug
>          Components: Install and Setup, Template
>    Affects Versions: pre-4.0.0
>         Environment: MS OS : Rhel 6.3 Hypervisor : vmware  Build : 
> http://jenkins.cloudstack.org/job/build-4.0-nonoss-rhel63/lastSuccessfulBuild/artifact/CloudStack-non-OSS-42.tar.bz2
>         [Git Revision: 9951d8973c046e7b258198342e0e746aa901e774 Git URL: 
> https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git ]
>            Reporter: Abhinav Roy
>            Priority: Blocker
>             Fix For: pre-4.0.0
>
>
> Description : 
> ====================== 
> Templates other than the systemvm template are not getting downloaded after 
> deploying an  Advanced zone CS setup with vmware 5.0 hypervisor. 
> Steps : 
> ====================== 
> Deploy a CS setup with vmware host using a non-oss build. 
> ====================== 
> Zone should be successfully deployed, system VMS should be created and the 
> default template should be deployed. 
> 1. Zone deployment is successful. 
> 2. system-vms get created successfully. 
> 3. But the problem is that there is no sign of deployment of any other 
> template (nothing seen in logs too), even if I try to manually register and 
> deploy a template it doesn't happen. 
> 4. Restarting system vm or management server doesn't change the behaviour.
> Here is the corresponding error in the system-vm logs :
> 2012-09-27 12:18:02,308 ERROR [cloud.agent.AgentShell] (Main :)  Unable to 
> start agent : Resource class not found: 
> com.cloud.storage.resource.PremiumSecondaryStorageResource due to : 
> java.lang.ClassNotFoundException: 
> com.cloud.storage.resource.PremiumSecondaryStorageResource

--
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

Reply via email to