Andrei, The 4.4.2 version sysvms report version 4.4.1. Unless you bake your own. I made some custom templates for xen and vmware for internal use. the 4.4.1 version should be fine though.
as for fix forward, going to 4.5 is an option but I meant keeping your own branch and cherry-picking fixes that you need until a new stable release is out. 4.4.3 was never voted in, but you could try that one On Wed, Feb 4, 2015 at 4:47 PM, Andrei Mikhailovsky <and...@arhont.com> wrote: > Actually, all my systemvms and VRs are running 4.4.1 eventhough I am sure > i've used the latest templates. Could someone running version 4.4.2 please > verify the version of their systemvms? > > Kind regards > > ----- Original Message ----- > >> From: "Pierre-Luc Dion" <pd...@cloudops.com> >> To: dev@cloudstack.apache.org >> Sent: Wednesday, 4 February, 2015 2:09:30 PM >> Subject: Re: Downgrading recommendations from 4.4.2 to 4.3.2 > >> Andrei, > >> I wouldn't recommend to downgrade, I did that in the past when we >> upgraded >> to 4.2.1 and I end up with even more issues. For the maintenance mode >> issue, can you verify that systemvm currently running (including VR) >> run as >> 4.4.2 ? I've saw behavior like this when upgrading to 4.4.x where >> CloudStack remain in Maintenance mode until all VR and system vm run >> to the >> proper ACS version. This is in /etc/cloudstack of VRs, cpvm and ssvm. >> if >> not at 4.4.2, try to install a new systemvm template and apply it to >> complete the upgrade of system VMs. > >> Hope this help and you won't have to deal with a rollback, if so, >> please >> share your experience > >> On Wed, Feb 4, 2015 at 8:51 AM, Andrei Mikhailovsky >> <and...@arhont.com> >> wrote: > >> > Daan, >> > >> > Do you mean that I should wait for the 4.5 branch to be out and try >> > an >> > upgrade hoping that the issues are fixed? >> > >> > Why do you think downgrading the database is a tricky business? >> > Let's say >> > I do the following: >> > >> > 1. Backup existing data base >> > 2. Remove all virtual routers >> > 3. remove the existing db (make a backup just in case). >> > 4. restore db from 4.3.2 >> > 5. downgrade packages >> > 6. restart networking (hopefully it will recreate all virtual >> > routers) >> > >> > Or do you think there might be some issues in this process? >> > >> > Thanks >> > >> > ----- Original Message ----- >> > >> > > From: "Daan Hoogland" <daan.hoogl...@gmail.com> >> > > To: "dev" <dev@cloudstack.apache.org> >> > > Sent: Wednesday, 4 February, 2015 12:34:08 PM >> > > Subject: Re: Downgrading recommendations from 4.4.2 to 4.3.2 >> > >> > > Andrei, >> > >> > > downgrading the database is your big problem. You don't want to >> > > restore at this point. I would go for fix forward but that's >> > > having >> > > the ability to maintain my own.branch. >> > >> > > On Wed, Feb 4, 2015 at 1:21 PM, Andrei Mikhailovsky >> > > <and...@arhont.com> wrote: >> > > > >> > > > >> > > > Hello guys, >> > > > >> > > > I was hoping to get some suggestions on how to perform a >> > > > downgrade >> > > > from a live 4.4.2 environment back to 4.3.2. After performing >> > > > an >> > > > upgrade 4 days ago, I have discovered a bunch of problems with >> > > > 4.4.2 release, which makes it unusable for me. Problems like >> > > > CLOUDSTACK-8201, CLOUDSTACK-8210 and inability to create new >> > > > instances (yet to open a support ticket) are kind of big issues >> > > > for me! >> > > > >> > > > Prior to performing an upgrade I've backed up cloud and >> > > > cloud_usage >> > > > databases of version 4.3.2. I have previously downgraded ACS >> > > > several times without any issues. However, i've done the >> > > > downgrade >> > > > a few hours after performing an upgrade. This time, it's been >> > > > about 4 days since i've done the upgrade. Since then, I've >> > > > restarted many networks with clean up enabled, which resulted >> > > > in >> > > > creation of new virtual routers. I've also created a few test >> > > > vms, >> > > > templates and snapshots, but I am not actually too concerned >> > > > about >> > > > those. >> > > > >> > > > What is the best route for me to do a downgrade to 4.3.2? I am >> > > > planning to do it this weekend, however, I can do it sooner. >> > > > Just >> > > > need to make sure my ACS will not be even more broken. >> > > > >> > > > Many thanks >> > > > >> > > > Andrei >> > > > >> > >> > > -- >> > > Daan >> > -- Daan
