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 jav
Hi,
Since a workaround available I don't think removing it is necessary.
However, I think users should be made aware via the site and 4.4
documentation that there is known issues and that upgrading is possibly
dangerous.
If you get hit by https://issues.apache.org/jira/browse/CLOUDSTACK-6893
there is no workaround in 4.4.0 as far as I know.
you can download the patch and apply it to 4.4.0 and rebuild, but then it
isn't 4.4.0 any more is it?
I've been hit by it in lab once, I don't know if it only happens in some
Daan,
In Japan, already some of press has announced 4.4 release and already some of
users tried this version so I think we should be keep expose 4.4 on site.
And if issues only depend on systemvm, It should be add note about links for
fixed systemvm template and explain workaround to avoid this
On Aug 1, 2014, at 4:56 AM, Daan Hoogland 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 t
On Fri, Aug 1, 2014 at 10:45 AM, Sebastien Goasguen wrote:
>
> On Aug 1, 2014, at 4:56 AM, Daan Hoogland 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 s
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 ins
