Re: [ovirt-users] 4.0 x 4.1

2017-01-25 Thread Pavel Gashev
Didi,

For example, BZ#1389251. It doesn’t look very serious. Actually “User is not 
able to edit her profile” is a side effect. Since users logged in by LDAP group 
permissions just did not have accounts in the engine, users did lose their 
access to created VMs after logout. This was a showstopper for me. Together 
with BZ#1382357 and BZ#1391146 User Portal was unusable. Fixes are simple and 
don’t affect the DB structure.

The latest nightly snapshot was broken by BZ#1402401 at the moment. I didn’t 
feel myself lucky enough to have the next snapshot without new regressions. So 
I had applied the fixes to 4.0.5.5.

-Original Message-
From: Yedidyah Bar David <d...@redhat.com>
Date: Tuesday 24 January 2017 at 23:51
To: Pavel Gashev <p...@acronis.com>
Cc: Karli Sjöberg <karli.sjob...@slu.se>, "users@ovirt.org" <users@ovirt.org>
Subject: Re: [ovirt-users] 4.0 x 4.1

On Tue, Jan 24, 2017 at 7:37 PM, Pavel Gashev <p...@acronis.com> wrote:
> Karli,
>
> You’re right. Actually, when I did encounter the bugs in 4.0.5, all of them 
> had been already found and fixed.

Actually, you can do that proactively - if you consider upgrading to
some version, you can search bugzilla for bugs targetted to the next
one, and if any of them look serious, wait.

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

See my earlier reply in this thread about the risks you take by doing that.

That said, if that's what you want, you can also use the 4.0 nightly snapshot:

https://www.ovirt.org/develop/dev-process/install-nightly-snapshot/

Was using this significantly different than what you built yourself?

Best,

>
> -Original Message-
> From: Karli Sjöberg <karli.sjob...@slu.se>
> Reply-To: Karli Sjöberg <karli.sjob...@slu.se>
> Date: Tuesday 24 January 2017 at 15:24
> To: "fernando.fredi...@upx.com.br" <fernando.fredi...@upx.com.br>, Pavel 
> Gashev <p...@acronis.com>, "users@ovirt.org" <users@ovirt.org>
> Subject: Re: [ovirt-users] 4.0 x 4.1
>
> On Tue, 2017-01-24 at 11:06 +, 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-boun...@ovirt.org> on behalf of Pavel Gashev <Pax@acroni
>> s.com>
>> Date: Tuesday 24 January 2017 at 13:38
>> To: Fernando Frediani <fernando.fredi...@upx.com.br>, "us...@ovirt.or
>> g" <users@ovirt.org>
>> 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-boun...@ovirt.org> on behalf of Fernando Frediani > ndo.fredi...@upx.com.br>
>> Date: Monday 23 January 2017 at 22:36
>> To: "users@ovirt.org" <users@ovirt.org>
>> 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@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users



-- 
Didi


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] 4.0 x 4.1

2017-01-24 Thread Yedidyah Bar David
On Tue, Jan 24, 2017 at 7:37 PM, Pavel Gashev <p...@acronis.com> wrote:
> Karli,
>
> You’re right. Actually, when I did encounter the bugs in 4.0.5, all of them 
> had been already found and fixed.

Actually, you can do that proactively - if you consider upgrading to
some version, you can search bugzilla for bugs targetted to the next
one, and if any of them look serious, wait.

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

See my earlier reply in this thread about the risks you take by doing that.

That said, if that's what you want, you can also use the 4.0 nightly snapshot:

https://www.ovirt.org/develop/dev-process/install-nightly-snapshot/

Was using this significantly different than what you built yourself?

Best,

>
> -Original Message-
> From: Karli Sjöberg <karli.sjob...@slu.se>
> Reply-To: Karli Sjöberg <karli.sjob...@slu.se>
> Date: Tuesday 24 January 2017 at 15:24
> To: "fernando.fredi...@upx.com.br" <fernando.fredi...@upx.com.br>, Pavel 
> Gashev <p...@acronis.com>, "users@ovirt.org" <users@ovirt.org>
> Subject: Re: [ovirt-users] 4.0 x 4.1
>
> On Tue, 2017-01-24 at 11:06 +, 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-boun...@ovirt.org> on behalf of Pavel Gashev <Pax@acroni
>> s.com>
>> Date: Tuesday 24 January 2017 at 13:38
>> To: Fernando Frediani <fernando.fredi...@upx.com.br>, "us...@ovirt.or
>> g" <users@ovirt.org>
>> 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-boun...@ovirt.org> on behalf of Fernando Frediani > ndo.fredi...@upx.com.br>
>> Date: Monday 23 January 2017 at 22:36
>> To: "users@ovirt.org" <users@ovirt.org>
>> 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@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users



-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] 4.0 x 4.1

2017-01-24 Thread Pavel Gashev
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.sjob...@slu.se>
Reply-To: Karli Sjöberg <karli.sjob...@slu.se>
Date: Tuesday 24 January 2017 at 15:24
To: "fernando.fredi...@upx.com.br" <fernando.fredi...@upx.com.br>, Pavel Gashev 
<p...@acronis.com>, "users@ovirt.org" <users@ovirt.org>
Subject: Re: [ovirt-users] 4.0 x 4.1

On Tue, 2017-01-24 at 11:06 +, 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-boun...@ovirt.org> on behalf of Pavel Gashev <Pax@acroni
> s.com>
> Date: Tuesday 24 January 2017 at 13:38
> To: Fernando Frediani <fernando.fredi...@upx.com.br>, "us...@ovirt.or
> g" <users@ovirt.org>
> 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-boun...@ovirt.org> on behalf of Fernando Frediani  ndo.fredi...@upx.com.br>
> Date: Monday 23 January 2017 at 22:36
> To: "users@ovirt.org" <users@ovirt.org>
> 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@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] 4.0 x 4.1

2017-01-24 Thread Yedidyah Bar David
On Tue, Jan 24, 2017 at 3:15 PM, Fernando Frediani
 wrote:
> Sounds reasonable.
>
> Out of curiosity what people use or do in order to rollback a failed upgrade

Usually engine-setup rolls back fine if it fails after it started
changing the system.

You can also backup the engine using engine-backup. If you then want
to downgrade,
you can use 'yum history' to undo the relevant transactions, then restore your
backup.

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

Indeed. You can use e.g. virt-manager or virsh for that.

You can even use a VM managed by another ovirt engine. I think that's
actually quite common.

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

IIRC this was discussed recently, and the bottom line was that this does not
work currently. I don't remember the details, perhaps you can search the
list archives.

>
> Thanks
>
> Fernando
>
>
>
> On 24/01/2017 05:03, Yedidyah Bar David wrote:
>>
>> On Mon, Jan 23, 2017 at 9:36 PM, Fernando Frediani
>>  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-management/
>>
>> 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,
>
>



-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] 4.0 x 4.1

2017-01-24 Thread Fernando Frediani

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
 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-management/

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,


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] 4.0 x 4.1

2017-01-24 Thread Karli Sjöberg
On Tue, 2017-01-24 at 11:06 +, 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-boun...@ovirt.org> on behalf of Pavel Gashev <Pax@acroni
> s.com>
> Date: Tuesday 24 January 2017 at 13:38
> To: Fernando Frediani <fernando.fredi...@upx.com.br>, "us...@ovirt.or
> g" <users@ovirt.org>
> 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-boun...@ovirt.org> on behalf of Fernando Frediani  ndo.fredi...@upx.com.br>
> Date: Monday 23 January 2017 at 22:36
> To: "users@ovirt.org" <users@ovirt.org>
> 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@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] 4.0 x 4.1

2017-01-24 Thread Pavel Gashev
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-boun...@ovirt.org> on behalf of Pavel Gashev <p...@acronis.com>
Date: Tuesday 24 January 2017 at 13:38
To: Fernando Frediani <fernando.fredi...@upx.com.br>, "users@ovirt.org" 
<users@ovirt.org>
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-boun...@ovirt.org> on behalf of Fernando Frediani 
<fernando.fredi...@upx.com.br>
Date: Monday 23 January 2017 at 22:36
To: "users@ovirt.org" <users@ovirt.org>
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@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] 4.0 x 4.1

2017-01-24 Thread Pavel Gashev
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-boun...@ovirt.org> on behalf of Fernando Frediani 
<fernando.fredi...@upx.com.br>
Date: Monday 23 January 2017 at 22:36
To: "users@ovirt.org" <users@ovirt.org>
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@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] 4.0 x 4.1

2017-01-23 Thread Yedidyah Bar David
On Mon, Jan 23, 2017 at 9:36 PM, Fernando Frediani
 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-management/

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,
-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] 4.0 x 4.1

2017-01-23 Thread Fernando Frediani
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@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users