incubator-cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pradeep Soundararajan (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-1252) Failed to download default template in VMware
Date Tue, 05 Mar 2013 18:34:13 GMT


Pradeep Soundararajan commented on CLOUDSTACK-1252:

The below entries are created during "mvn -P systemvm -Dnonoss install" build for the respective
master and 4.1 builds.  I am able to grep for all vmware related jars from these zip files.



During packaging I am seeing the same vmware jars are not available in  which
is present under <workspace>/dist/rpmbuild/BUILDROOT/cloudstack-4.2.0-SNAPSHOT.el6.x86_64/usr/share/cloudstack-common/vms/

diff -b services/console-proxy/server/dist/  dist/rpmbuild/BUILDROOT/cloudstack-4.2.0-SNAPSHOT.el6.x86_64/usr/share/cloudstack-common/vms/
Binary files services/console-proxy/server/dist/ and dist/rpmbuild/BUILDROOT/cloudstack-4.2.0-SNAPSHOT.el6.x86_64/usr/share/cloudstack-common/vms/

I think that is the reason behind this issue.  *vmware*.jar are not getting copied to
during package creation.

> Failed to download default template in VMware
> ---------------------------------------------
>                 Key: CLOUDSTACK-1252
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM, VMware
>    Affects Versions: 4.1.0
>         Environment: CentOS6.3
> 4.1 branch build
> Hyper visor : VMware 
>            Reporter: Rayees Namathponnan
>            Assignee: Pradeep Soundararajan
>            Priority: Blocker
>             Fix For: 4.1.0
>         Attachments: cloud.rar
> Step 1 : Created new build from 4.1 branch 
> Step 2 : Install and configured MS server on CentOS 6.3 
> Step 3 : Prepared system template and created advanced zone
> Actual result 
> System VM are created, but "default templates" are not available in template section.
> I tried to started agent from SSVM, with command ">service cloudstack-agent start"
and failed, 
>  but command ">service cloud start" works
> If you look at the SSVM cloud.out (/var/log/cloud/clout.out) you can see class not found
exception java.lang.ClassNotFoundException:
> + java -mx168m -cp ./:./conf:aopalliance-1.0.jar:apache-log4j-extras-1.1.jar:aspectjrt-1.7.1.jar:aspectjweaver-1.7.1.jar:aws-java-sdk- template=domP type=secstorage host= port=8250 name=s-3-VM
zone=1 pod=1 guid=s-3-VM
instance=SecStorage sslcopy=true role=templateProcessor mtu=1500 eth2ip= eth2mask=
gateway= eth0mask= eth0ip= eth1ip=
eth1mask= mgmtcidr= localgw=
eth3ip= eth3mask= storageip= storagenetmask=
storagegateway= internaldns1= internaldns2= dns1=
> log4j:WARN No appenders could be found for logger (org.apache.commons.httpclient.params.DefaultHttpParams).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See for more info.
> Unable to start agent: Resource class not found:
due to: java.lang.ClassNotFoundException:
> Attached cloud.out for reference 

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:

View raw message