Upgrading CloudStack without new systemvm template in place

[Pierre-Luc Dion <pd...@cloudops.com>]

I've filled a bug regarding CloudStack Upgrade since 4.3.
when Upgrading to 4.3, 4.4.0 4.4.1  you have to create sysvm template
named  systemvm-<hypervisor>-4.3
otherwise, right after the database upgrade the management-server fail to
start (restart hs well).

The idea is quite good, but it should not break cloudstack if the
systemvm-template is absent. A problem I can see is if someone perform a
general os upgrade and it upgrade cloudstack by accident, it can break
cloudstack management server.

https://issues.apache.org/jira/browse/CLOUDSTACK-7365

is this something that could be fixed in 4.4.1 ?

Thanks,

*Pierre-Luc DION*
Architecte de Solution Cloud | Cloud Solutions Architect
t 855.652.5683

*CloudOps* Votre partenaire infonuagique* | *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_