venkata swamybabu budumuru created CLOUDSTACK-1994:
------------------------------------------------------
Summary: [SSVM] Unable to start agent: Resource class not found:
org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource due to:
java.lang.ClassNotFoundException:
org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource
Key: CLOUDSTACK-1994
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1994
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Storage Controller
Affects Versions: 4.2.0
Environment: commit 97c2f7d0c4b330f3456e8c1b5236e280b9931197
Reporter: venkata swamybabu budumuru
Priority: Blocker
Fix For: 4.2.0
Steps to reproduce :
1. Have the latest master and deploy an advanced zone with Xen Cluster
2. use system vm template "systemvmtemplate-2013-03-27-master-xen.vhd.bz2" from
http://jenkins.cloudstack.org
3. verify whether system vms come up fine or not
Observations :
(i) both v-2-VM and s-1-VM are shown in running state
(ii) cloud.host table doesn't show the SSVM but, shows the console proxy in
host table.
(iii) Here is the snippet from SSVM:/var/log/cloud/cloud.out
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 http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
info.
08:15:40,493 ERROR AgentShell:610 - Unable to start agent: Resource class not
found: org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource due
to: java.lang.ClassNotFoundException:
org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource
Unable to start agent: Resource class not found:
org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource due to:
java.lang.ClassNotFoundException:
org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource
Attaching all the required logs to bug.
--
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
