cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From benoit lair <kurushi4...@gmail.com>
Subject Re: [ACS44]{DISCUSS] remove from the site
Date Mon, 04 Aug 2014 09:22:34 GMT
Hello


Haven't we got a very similar problem when upgrading from acs 4.2 to acs
4.3 ? From my memories, we had to apply a trick in order to get working the
system vm template after upgrading the acs version.

I do not see this as a blocking step for a production environment. If there
is in the installation upgrade process the notice with a tutorial
explaining why and how to do it securely, so we can prepare smoothly our
upgrade, isn't it ?


2014-08-01 16:55 GMT+02:00 David Nalley <david@gnsa.us>:

> On Fri, Aug 1, 2014 at 10:45 AM, Sebastien Goasguen <runseb@gmail.com>
> wrote:
> >
> > On Aug 1, 2014, at 4:56 AM, Daan Hoogland <daan.hoogland@gmail.com>
> wrote:
> >
> >> H,
> >>
> >> In the last couple of days a lot of problems with 4.4.0 have been
> >> reported. Workarounds, if at all available, are hard and require
> >> intimate sysadmin experience. It seems to me we didn't deliver the
> >> quality we want to.
> >>
> >> One of the problems is that the systemvms need an upgrade because of
> >> our java 1.7 usage which poses a potential bootstrap problem in case
> >> the secondary storage vm is rebooted/restarted. A possible solution
> >> would be to have the svm do an update on the java packages with ssh
> >> during the upgrade of the management server.
> >> Concequential problem is that the upgrade of the systemvms at this
> >> moment requires manual intervention of the operator, as the upgrade
> >> code as used in the case of 4.3 has not been created for this version.
> >> A workaround is here:
> >> https://gist.github.com/terbolous/102ae8edd1cda192561c/
> >>
> >> SO I wonder if we should still expose the world to version 4.4.0
> >>
> >> thoughts?
> >
> > Haven't tried upgrade, but if there is an issue (and it seems like there
> is), then we should release 4.4.1 asap.
> > And inform users@ of the problem...
> >
>
> Agreed.
> We can't undo 4.4.0 - we can delay promoting the 4.4 release until
> 4.4.1 is available.
>
> --David
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message