mirror of https://github.com/apache/cloudstack.git
9fa3f92efd
- In the upgrade, new XenServer template entry was added in vm_template having id=100 - However we already have another System VM XenServer template downloaded in the upgrade process that gets different id. - SSVM could not start because the vm_instance's templateId after the upgrade was set to '100' with the assumption that the Xenserver template with id=100 will be used. Fix to upgrade script is: - we should not insert any entry in vm_template table for XenServer systemVM via the upgrade DB script. The latest XenServer template will get added in the upgrade process having name 'routing-xenserver-2.2.4'. - we should update the system VM's template_id in vminstance table to point to this ''routing-xenserver-2.2.4' template. |
||
|---|---|---|
| .. | ||
| bindir | ||
| db | ||
| .project | ||