I am deploying a oVirt environment which will not get production data immediately. Obviously I would rather use 4.1 RC due the many changes and fixes present. Later when 4.1 becomes stable then upgrade to it. Does anyone see any problem in doing that way or would it be more advisable to start with 4.0.6 and upgrade to 4.1 stable when time comes ?

My concern are the issue people related they had when upgrading from one major version to another in the past.

Sounds reasonable. Out of curiosity what people use or do in order to rollback a failed upgrade

or an upgrade that can bring instability in the control or operation of the cluster ? In VMware as vCenter used to run within a Virtual Machine I used to take a snapshot before starting the upgrade. In oVirt if I have my Engine running in a simple VM somewhere else out of the cluster as well I guess that could also be an option.

What about when it is a self hosted engine. Would it work ?

Thanks Fernando On 24/01/2017 05:03, Yedidyah Bar David wrote: > > On Mon, Jan 23, 2017 at 9:36 PM, Fernando Frediani > <fernando.frediani(a)upx.com.br&gt; wrote: >> >> I am deploying a oVirt environment which will not get production data >> immediately. >> >> Obviously I would rather use 4.1 RC due the many changes and fixes >> present. >> Later when 4.1 becomes stable then upgrade to it. >> Does anyone see any problem in doing that way or would it be more >> advisable >> to start with 4.0.6 and upgrade to 4.1 stable when time comes ? > > If eventually it will be production, I'd start with 4.0.6. > > Generally speaking, if we find in the future a bug when upgrading from > 4.0.6 to 4.1.z, we'll try to solve it, so that it does not affect an > upgrade from 4.0.6 to 4.1.z+1. But if we find a bug that affects only > upgrade from a rc/beta/etc. version to a stable version, we might decide > it's not worth fixing. > > Also note that 4.1.0 should be out really soon: > > > https://www.ovirt.org/develop/release-management/releases/4.1/release-man... > > So you might as well simply wait a bit. > >> My concern are the issue people related they had when upgrading from one >> major version to another in the past. > > In general, or to/from beta/rc/etc versions? > > In general we appreciate very much people testing upgrades from/to beta/rc > versions, and if they find bugs, we do try to fix them. But people should > do this in test environments, not ones that are eventually destined to > become > production. > > Best,

I'd like to apologize for 'ugly' word. From my own personal experience 4.0.5 had some bugs which spoiled my impression from 4.0. Fortunately most of them are fixed in 4.0.6.

-----Original Message----- From: <users-bounces(a)ovirt.org&gt; on behalf of Pavel Gashev <Pax@acroni s.com> Date: Tuesday 24 January 2017 at 13:38 To: Fernando Frediani <fernando.frediani(a)upx.com.br&gt;, &quot;users(a)ovirt.or g" <users(a)ovirt.org&gt; Subject: Re: [ovirt-users] 4.0 x 4.1 I started with oVirt 3.6. It became stable since 3.6.7 just when 4.0 is released. Also I use 4.0. The previous 4.0.5 was ugly, 4.0.6 can be considered more or less stable, and 4.1 is going to be released soon. Thus, I’d start with 4.0 and upgrade to 4.1 when 4.2 is released. -----Original Message----- From: <users-bounces(a)ovirt.org&gt; on behalf of Fernando Frediani <ferna ndo.frediani(a)upx.com.br&gt; Date: Monday 23 January 2017 at 22:36 To: &quot;users(a)ovirt.org&quot; <users(a)ovirt.org&gt; Subject: [ovirt-users] 4.0 x 4.1 I am deploying a oVirt environment which will not get production data immediately. Obviously I would rather use 4.1 RC due the many changes and fixes present. Later when 4.1 becomes stable then upgrade to it. Does anyone see any problem in doing that way or would it be more advisable to start with 4.0.6 and upgrade to 4.1 stable when time comes ? My concern are the issue people related they had when upgrading from one major version to another in the past. Thanks Fernando _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

Karli, You’re right. Actually, when I did encounter the bugs in 4.0.5, all of them had been already found and fixed.

No doubt that developers do their hard job well. Unfortunately, due to the holydays there was a two-month gap between releases. 4.0.6-pre had another issue. I personally had to build my own hot-fix oVirt release with all the fixes and without changes under development. I can only guess what other users experienced.

-----Original Message----- From: Karli Sjöberg <karli.sjoberg(a)slu.se&gt; Reply-To: Karli Sjöberg <karli.sjoberg(a)slu.se&gt; Date: Tuesday 24 January 2017 at 15:24 To: &quot;fernando.frediani(a)upx.com.br&quot; <fernando.frediani(a)upx.com.br&gt;, Pavel Gashev <Pax(a)acronis.com&gt;, &quot;users(a)ovirt.org&quot; <users(a)ovirt.org&gt; Subject: Re: [ovirt-users] 4.0 x 4.1 On Tue, 2017-01-24 at 11:06 +0000, Pavel Gashev wrote: > I'd like to apologize for 'ugly' word. From my own personal > experience 4.0.5 had some bugs which spoiled my impression from 4.0. > Fortunately most of them are fixed in 4.0.6. I should really not throwing stone in glass houses here, since we´re still running 3.6 (I know, I know), but... If everyone thought like that, no one would have tested and gotten those bugs fixed in 4.0.6 either, see what I´m saying? So if people hadn´t tested and bug-reported those things, your impression of 4.0.6 would probably have been just as bad. Just my two cents. /K > > -----Original Message----- > From: <users-bounces(a)ovirt.org&gt; on behalf of Pavel Gashev <Pax@acroni > s.com> > Date: Tuesday 24 January 2017 at 13:38 > To: Fernando Frediani <fernando.frediani(a)upx.com.br&gt;, &quot;users(a)ovirt.or > g" <users(a)ovirt.org&gt; > Subject: Re: [ovirt-users] 4.0 x 4.1 > > I started with oVirt 3.6. It became stable since 3.6.7 just when 4.0 > is released. Also I use 4.0. The previous 4.0.5 was ugly, 4.0.6 can > be considered more or less stable, and 4.1 is going to be released > soon. Thus, I’d start with 4.0 and upgrade to 4.1 when 4.2 is > released. > > -----Original Message----- > From: <users-bounces(a)ovirt.org&gt; on behalf of Fernando Frediani <ferna > ndo.frediani(a)upx.com.br&gt; > Date: Monday 23 January 2017 at 22:36 > To: &quot;users(a)ovirt.org&quot; <users(a)ovirt.org&gt; > Subject: [ovirt-users] 4.0 x 4.1 > > I am deploying a oVirt environment which will not get production > data > immediately. > > Obviously I would rather use 4.1 RC due the many changes and fixes > present. Later when 4.1 becomes stable then upgrade to it. > Does anyone see any problem in doing that way or would it be more > advisable to start with 4.0.6 and upgrade to 4.1 stable when time > comes ? > > My concern are the issue people related they had when upgrading from > one > major version to another in the past. > > Thanks > > Fernando > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users