mirror of https://github.com/apache/cloudstack.git
3ad19c633f
- 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. |
||
|---|---|---|
| .. | ||
| db | ||
| 22beta4to22GA.sql | ||
| 221to222.sql | ||
| 221to222_usage.sql | ||
| 221to222upgrade.sh | ||
| create-database.sql | ||
| create-index-fk.sql | ||
| create-schema.sql | ||
| data-20to21.sql | ||
| data-22beta1to22beta2.sql | ||
| deploy-db-dev.sh | ||
| index-20to21.sql | ||
| index-212to213.sql | ||
| postprocess-20to21.sql | ||
| server-setup.sql | ||
| server-setup.xml | ||
| templates.kvm.sql | ||
| templates.sql | ||
| templates.vmware.sql | ||
| templates.xenserver.sql | ||