[
https://issues.apache.org/jira/browse/CLOUDSTACK-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236780#comment-14236780
]
Rohit Yadav commented on CLOUDSTACK-8041:
-----------------------------------------
Went through the logs and upgrade class, we simply need to document the upgrade
process when upgrading to 4.5.0 similar to:
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/stable/upgrade/upgrade-4.4.0.html#update-system-vm-templates
Another solution is: cc [~dahn]
In the Upgrade442to450 class's updateSystemVmTemplates, instead of updating
systevms with new url/checksum in the end when a systemvm is not found for a
hypervisor in use; we can start by updating vm_template table with the new
templates only if a new template is not found and then continue with the
upgrade logic. This way we are sort of registering the template in case a
sysadmin forgot to register a template.
> 4.5.0 db upgrade fail if new systemvm templates are abscent
> ------------------------------------------------------------
>
> Key: CLOUDSTACK-8041
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8041
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.5.0
> Reporter: Pierre-Luc Dion
> Priority: Blocker
> Fix For: 4.5.0, 4.6.0
>
>
> When upgrading ACS to 4.5.0 without systemvm-{hypervisor}-4.5 already in
> place, the db upgrade fail.
> Upgrading ACS without systemvm should not affect db upgrade.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
