----- Original Message -----
From: "Itamar Heim" <iheim(a)redhat.com>
To: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com>
Cc: "Mike Burns" <mburns(a)redhat.com>, board(a)ovirt.org, "users"
<users(a)ovirt.org>
Sent: Wednesday, October 16, 2013 3:12:34 AM
Subject: Re: [Users] oVirt Weekly Meeting Minutes -- 2013-10-09
On 10/15/2013 04:40 AM, Gianluca Cecchi wrote:
> On Wed, Oct 9, 2013 at 5:15 PM, Mike Burns wrote:
>
>> * 3.3 updates (mburns, 14:08:42)
>> * 3.3.0.1 vdsm packages are posted to updates-testing (mburns,
>> 14:09:04)
>
> Hello,
> having 3.3.0-4 on fedora 19, can you explain correct steps to test 3.3.0.1?
> Is only a matter of updating packages or is engine-upgrade command
> involved?
> Need to redeploy hosts or only update their packages after enabling
> updates-testing?
>
> Gianluca
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/users
>
yum update + engine-upgrade for engine.
Actually engine-upgrade is deprecated in 3.3 and its function is fulfilled
by engine-setup, which also does upgrades. Currently, running engine-upgrade
will emit some informational message, and will probably be removed altogether
in 3.4.
--
Didi