On Aug 1, 2014, at 4:56 AM, Daan Hoogland <daan.hoogl...@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... > -- > Daan
