I tried upgrade from 4.0 -> 4.1 using Rhel6.3 binaries for Management server
and KVM hosts in Advanced zone set up.
I had an issue with KVM agent upgrade. After upgrading the binaries on KVM host
, cloudstack-agent fails to start.
This was because agent.properties is not restored as part of upgrading the
binaries from 4.0 to 4.1.
Once I restored the agent.properties manually , cloudstack-agent was able to
start successfully.
After upgrade , I was able to deploy Vms in new network without any issues.
Following are the issues that were found during upgrade testing:
CLOUDSTACK-1844 - Upgrade 4.0 -> 4.1 - KVM host agent.properties is not
restored as part of upgrading the binaries from 4.0 to 4.1.
When DB dump checks between upgraded setup and freshly installed 4.1 set up
were done , following issues were noted:
CLOUDSTACK-1842 - ASF 4.0 to 4.1 Upgrade: Missing Ubuntu 12.04 Guest OS
Types on the Upgraded Setup
CLOUDSTACK-1841 - ASF 4.0 to 4.1 Upgrade: Missing Few Global
Configuration parameters on the Upgraded Setup
CLOUDSTACK-1839 - Upgrade 4.0 -> 4.1 - Upgraded DB has lot more keys
and indexes for many tables compare to the fresh installed 4.1 DB.
-Thanks
Sangeetha
-----Original Message-----
From: Sangeetha Hariharan [mailto:sangeetha.hariha...@citrix.com]
Sent: Thursday, March 28, 2013 1:22 PM
To: Chip Childers
Cc: dev@cloudstack.apache.org
Subject: RE: [ACS41][QA] Has anyone upgraded from 4.0 to 4.1
Create a doc bug for documenting these steps - CLOUDSTACK-1837 - Additonal
Steps ( Restart of all system Vms , copy vhd-utils) to be included in the
upgrade procedure from 4.0 -> 4.1
-Thanks
Sangeetha
-----Original Message-----
From: Chip Childers [mailto:chip.child...@sungard.com]
Sent: Thursday, March 28, 2013 12:18 PM
To: Sangeetha Hariharan
Cc: dev@cloudstack.apache.org
Subject: Re: [ACS41][QA] Has anyone upgraded from 4.0 to 4.1
On Thu, Mar 28, 2013 at 11:28:33AM -0700, Sangeetha Hariharan wrote:
> Then we can go with the option of reboot (start and stop) of all the system
> Vms (SSVM,CPVM and routers) as part of Upgrade procedure ?
Sounds like it. Care to add a note to the release notes wiki page to this
effect?
>
> -Thanks
> Sangeetha
>
> -----Original Message-----
> From: Marcus Sorensen [mailto:shadow...@gmail.com]
> Sent: Thursday, March 28, 2013 11:21 AM
> To: Chip Childers
> Cc: dev@cloudstack.apache.org
> Subject: Re: [ACS41][QA] Has anyone upgraded from 4.0 to 4.1
>
> I'm also not confident that option 1 really fixes anything. The user has to
> reboot their system VMS eventually, and even if we fix this one thing to help
> them get by until they do, what other lingering issues will arise?
> On Mar 28, 2013 11:38 AM, "Chip Childers" <chip.child...@sungard.com> wrote:
>
> > On Thu, Mar 28, 2013 at 09:51:16AM -0700, Sangeetha Hariharan wrote:
> > > Can we get a confirmation on the approach we want to take?
> > >
> > > 1. We are going to fix the router for the case - " if the router
> > > has
> > upgraded its scripts, and then adjust how we call edithosts.sh" ?
> > > 2. Going to suggest a reboot (start and stop) of all the system
> > > Vms
> > (SSVM,CPVM and routers) as part of Upgrade procedure?
> >
> > Option 2 is my preference. Option 1 requires more testing, etc...
> >
>
