Is there are fix or workaround for the Ovirt 3.3 Cluster and VDSM 4.14?
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!
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. 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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
----- Original Message -----
From: "Lior Vernia" <lvernia@redhat.com> To: "Drew Showers" <drew@augurworks.com> Cc: users@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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Thank you for the replies! Since it was back ported, is there an rpm package update for 3.3? On Mon, Apr 21, 2014 at 6:17 PM, Eli Mesika <emesika@redhat.com> wrote:
----- Original Message -----
From: "Lior Vernia" <lvernia@redhat.com> To: "Drew Showers" <drew@augurworks.com> Cc: users@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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
I just see a "backport" for engine 3.4 not for engine 3.3 Am I missing something? In which 3.3.x release was this fixed? Am 22.04.2014 00:17, schrieb Eli Mesika:
The correct BZ fixing this issue is BZ 1067096 and it was back-ported in commit 1f86f681e8a6e11f2b026ff7bdc579ccf5edeac9
-- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
----- Original Message -----
From: "Sven Kieske" <S.Kieske@mittwald.de> To: users@ovirt.org, "Eli Mesika" <emesika@redhat.com> Sent: Tuesday, April 22, 2014 9:42:43 AM Subject: Re: [ovirt-users] Is there are fix or workaround for the Ovirt 3.3 Cluster and VDSM 4.14?
I just see a "backport" for engine 3.4 not for engine 3.3
Am I missing something? In which 3.3.x release was this fixed?
We didn't fixed that for 3.3.z , BZ had no Z stream flag ...
Am 22.04.2014 00:17, schrieb Eli Mesika:
The correct BZ fixing this issue is BZ 1067096 and it was back-ported in commit 1f86f681e8a6e11f2b026ff7bdc579ccf5edeac9
-- Mit freundlichen Grüßen / Regards
Sven Kieske
Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
participants (4)
-
Drew Showers -
Eli Mesika -
Lior Vernia -
Sven Kieske