[ https://issues.apache.org/jira/browse/CLOUDSTACK-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706822#comment-13706822 ]
Abhinandan Prateek edited comment on CLOUDSTACK-3480 at 7/12/13 9:39 AM: ------------------------------------------------------------------------- -- was (Author: aprateek): The db template path is actually not used for seeding system VM templates. > Correct the templates.sql to point to right systemvm templates > -------------------------------------------------------------- > > Key: CLOUDSTACK-3480 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3480 > 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 > Reporter: Prasanna Santhanam > Priority: Critical > Fix For: 4.2.0 > > > When using NFS as a secondary storage we are required to place systemVM > templates for the initial bootstrap of the service VMs (CPVM, SSVM). This is > not a mandatory step when using object storage as a backing image store. In > the > case of object store we download the templates as listed in the vm_template > table for the hypervisor we are dealing with. The source of the entires is in > the templates.sql file. Since systemVM templates have undergone changes from > 3.0.2 (from when the template entires exist in vm_template) it is best to > update these to the latest available locations for the systemVM templates. > One instance that will not work is the KVM clock sync that requires the newer > systemVM template to exist. -- 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