----- Original Message -----
From: "Lior Vernia" <lvernia(a)redhat.com>
To: "Drew Showers" <drew(a)augurworks.com>
Cc: users(a)ovirt.org
Sent: Monday, April 21, 2014 10:50:59 AM
Subject: Re: [ovirt-users] Is there are fix or workaround for the Ovirt 3.3 Cluster and
VDSM 4.14?
Hi!
An upgrade would fix it. The general issue hasn't yet been fixed
(looking at BZ 1077110) and I don't know whether it'll be backported
when it does.
The correct BZ fixing this issue is BZ 1067096 and it was back-ported in commit
1f86f681e8a6e11f2b026ff7bdc579ccf5edeac9
I would edit the engine's DB and append "4.14" to the option_value
column of the vdc_options table where
option_name="SupportedVDSMVersions", then restart the engine. I think
this should be enough.
Yours, Lior.
On 20/04/14 17:45, Drew Showers wrote:
> I know this error has been noted and a BZ bug logged. However, is there
> a fix or workaround yet for 3.3? Or do I need to upgrade to 3.4?
>
> Thanks in advance!
>
>
>
> _______________________________________________
> 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