Hi Asanka, Agree with Eric, doesn’t look right.,
The quickest solution here is to: 1) disable zone 2) delete system VMs 3) remove secondary storage from cloudstack 4) try the secondary storage seeding again with images from http://packages.shapeblue.com/systemvmtemplate/4.6/new/ - but use the “-F” option when you call /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt > this will clean up previous template 5) add secondary storage to CloudStack again 6) enable zone and monitor Regards, Dag Sonstebo Cloud Architect ShapeBlue On 18/08/2017, 18:35, "Eric Green" <[email protected]> wrote: [email protected] www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue > On Aug 18, 2017, at 03:22, Asanka Gunasekara <[email protected]> wrote: > > Hi Eric, > > SSVM can access my nfs and I an manual mount :( > > This "s-397-VM:/# grep com.cloud.agent.api.SecStorageSetupCommand /var/log/cloud.log" did not produced any output, but found below error > > From the VM's /var/log/cloud.log: > ERROR [cloud.agent.AgentShell] (main:null) Unable to start agent: Resource class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource due to: java.lang.ClassNotFoundException: com.cloud.storage.resource.PremiumSecondaryStorageResource Hmm. That doesn't look good. So the agent is never even able to start because of that exception. This looks like a mismatch between your SSVM template and your version of Cloudstack. It looks like you're using a version of Cloudstack that has been compiled with premium features that is expecting a template that supports premium features. Someone else will have to tell you how to change the SSVM template, I don't know that. Or since this is a zone that has never been operational, you may choose to simply wipe the current install entirely and start over again from scratch with a Cloudstack and SSVM template all from the same source. Remember to drop and recreate the database as part of that process, as well as remove all the contents of the secondary store and follow the directions again to reinitialize with the initial template. For the record, I got my Cloudstack from this source: [cloudstack] name=cloudstack baseurl=http://cloudstack.apt-get.eu/centos/$releasever/4.9/ enabled=1 gpgcheck=0 My template similarly came from that source (but the 4.6 version, as you specified). Once I got my networking sorted out, which you seem to have done, it Just Worked.
