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... > > >
