[
https://issues.apache.org/jira/browse/CLOUDSTACK-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236814#comment-14236814
]
Pierre-Luc Dion commented on CLOUDSTACK-8041:
---------------------------------------------
I'd like to avoid the need to have a systemvm-template for each upgrade, as
this RN:
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4.2/upgrade/upgrade-4.2.html
Now with 4.5, a user upgrading from 4.2.1 to 4.5 need to register 3
systemvm-templates prior to upgrade, and they cannot be deleted from the ui
afterward.
> 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)
