Except heartbleed fix. I was merely checking if it's even poosible to do an automated upgrade.
The way i know the upgrade process we add some sql magic to check for new systemvm templates. If that's not made for 4.3.1 it won't do much good to add it as systemvm-hypervisor-version. Erik 11. sep. 2014 15:45 skrev "Wei ZHOU" <ustcweiz...@gmail.com> følgende: > As far as I know, there is no systemvm change during upgrade from 4.3.0 to > 4.3.1 > > 2014-09-11 15:22 GMT+02:00 Erik Weber <terbol...@gmail.com>: > > > On Thu, Sep 11, 2014 at 3:01 PM, Nux! <n...@li.nux.ro> wrote: > > > > > Hello, > > > > > > I've upgraded and it looks ok for now. > > > I have used these system VMs > > > http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/ > and > > > added them as systemvm-kvm-4.3 in the Templates. > > > I expected them to replace SystemVM Template (KVM), but they are still > > > listed as systemvm-kvm-4.3 alongside the old ones. > > > Other than that everything seems ok for now. > > > > > > > > Is there an upgrade path from 4.3.0 systemvm template to 4.3.1? Log on > to a > > newly deployed one and check /etc/cloudstack-version > > > > -- > > Erik > > >
