[
https://issues.apache.org/jira/browse/CLOUDSTACK-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236773#comment-14236773
]
Rohit Yadav commented on CLOUDSTACK-8041:
-----------------------------------------
Can we have this kind of fix (cc [~dahn]):
For each Upgrade4xxto4yy classes, if the DB destination version for that
particular db upgrade class is not the final upgrade version (which is same as
the war/jar version of the new/upgraded CloudStack), we skip the rule where it
throws exception if systemvms are missing we ignore and continue. We can
further skip if any systevms is available sharing the same major version (i.e.
if upgrading to 4.5.1 in future and 4.5.0 systemvm template is present we don't
need to run the systemvm rule have 4.5.1 systemvm template). This will simply
mean that now (and in future), when upgrading sysadmins will only need to
register systemvms for the CloudStack (major) version they are upgrading to.
Comment?
> 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: Critical
> 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)
