Well, that didn't go so well. Trying to "hotfix" the 4.4.1 systemvm resulted in successfull SSVM and CP VMs to be restarted, however the VR upgrade went bad: http://pastebin.com/raw.php?i=SB3tYHZc
I'll try to downgrade to the 4.4.0 Sys VM and see if that will work. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "Nux!" <n...@li.nux.ro> > To: dev@cloudstack.apache.org > Sent: Tuesday, 21 October, 2014 21:25:41 > Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1? > So what I see has happened is as a result of the DB upgrade from 4.3.1 to > 4.4.1 > the systemvm-kvm-4.4 (4.4.0-6) has been marked of type System, it's not > deletable now. > Also its ID in the DB is now present as the template to use for ConsoleProxy, > SSVM and VR. > It's as if the hotfix was performed, although I have most certainly not. > > Can I just go ahead and perform the hotfix manually, but for > systemvm-kvm-4.4.1 > instead of systemvm-kvm-4.4? > I imagine it should just work, but would not rather take my chances at pulling > another long night. :) > > Lucian > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > > ----- Original Message ----- >> From: "Nux!" <n...@li.nux.ro> >> To: dev@cloudstack.apache.org >> Sent: Tuesday, 21 October, 2014 21:12:28 >> Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1? > >> Well, hit a small issue: >> - added 4.4.0 systemvm - OK >> - upgraded management/db - OK >> - add 4.4.1 systemvm - FAIL - "Cannot use reserved names for templates" >> >> So the names from the 4.4.0 and 4.4.1 systemvm names are identical and >> conflict. >> I added the 4.4.1 systemvm as systemvm-kvm-4.4.1. Would this work? >> >> -- >> Sent from the Delta quadrant using Borg technology! >> >> Nux! >> www.nux.ro >> >> ----- Original Message ----- >>> From: "Nux!" <n...@li.nux.ro> >>> To: dev@cloudstack.apache.org >>> Sent: Tuesday, 21 October, 2014 20:43:41 >>> Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - >>> 4.4.1? >> >>> Ok, cheers. I'll start shortly, fingers crossed. :) >>> >>> -- >>> Sent from the Delta quadrant using Borg technology! >>> >>> Nux! >>> www.nux.ro >>> >>> ----- Original Message ----- >>>> From: "Daan Hoogland" <daan.hoogl...@gmail.com> >>>> To: "dev" <dev@cloudstack.apache.org> >>>> Sent: Tuesday, 21 October, 2014 20:39:50 >>>> Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - >>>> 4.4.1? >>> >>>> it most certainly does >>>> >>>> On Tue, Oct 21, 2014 at 9:38 PM, Nux! <n...@li.nux.ro> wrote: >>>>> Right, so the steps would be: >>>>> >>>>> - install 4.4.0-6 systemvm >>>>> - upgrade management/db >>>>> - install 4.4.1 systemvm >>>>> - do the manual db hotfix thing >>>>> - finally restart the systemvms so they use the 4.4.1 template >>>>> >>>>> Does that cover it? >>>>> >>>>> -- >>>>> Sent from the Delta quadrant using Borg technology! >>>>> >>>>> Nux! >>>>> www.nux.ro >>>>> >>>>> ----- Original Message ----- >>>>>> From: "Daan Hoogland" <daan.hoogl...@gmail.com> >>>>>> To: "dev" <dev@cloudstack.apache.org> >>>>>> Sent: Tuesday, 21 October, 2014 20:35:51 >>>>>> Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - >>>>>> 4.4.1? >>>>> >>>>>> On Tue, Oct 21, 2014 at 9:32 PM, Nux! <n...@li.nux.ro> wrote: >>>>>>> ual sys >>>>>> >>>>>> >>>>>> that would be once you install the 4.4.1 templates, yes. remind me >>>>>> often we need to upgrade the systemvm upgrade mechs >>>>>> >>>>>> -- >>>>>> Daan >>>> >>>> >>>> >>>> -- > > > > Daan
