Hi Francesco ,
I'm using libvirt-1.2.8-16.el7.x86_64 in all my hosts in 3.6 cluster.
And it's still the same.
Thanks :)
----- Original Message -----
From: "Francesco Romani" <fromani(a)redhat.com>
To: "Michael Burman" <mburman(a)redhat.com>
Cc: "Oved Ourfali" <oourfali(a)redhat.com>, "ybronhei"
<ybronhei(a)redhat.com>, devel(a)ovirt.org, infra(a)ovirt.org
Sent: Thursday, February 12, 2015 1:36:09 PM
Subject: Re: [ovirt-devel] Can't join vdsm(4.17.0-390.gita3163f3.el7.x86_64) to
Cluster 3.6
----- Original Message -----
From: "Michael Burman" <mburman(a)redhat.com>
To: "Oved Ourfali" <oourfali(a)redhat.com>, "ybronhei"
<ybronhei(a)redhat.com>
Cc: devel(a)ovirt.org, infra(a)ovirt.org
Sent: Thursday, February 12, 2015 10:39:54 AM
Subject: Re: [ovirt-devel] Can't join vdsm(4.17.0-390.gita3163f3.el7.x86_64) to
Cluster 3.6
By the way,
Every time that i'm running update to vdsm 4.17.0 (and it's every morning) ,
Host goes to non-operational state cause the 3.6 support for engine and
cluster deleted from the dsaversion.py file after every vdsm update, and
needed to edited manually again and again.
Easiest -and definitive- way to fix that is just upgrade libvirt to anything >= 1.2.3.
Is that feasible for you?
Bests,
--
Francesco Romani
RedHat Engineering Virtualization R & D
Phone: 8261328
IRC: fromani
--
Michael Burman
Intern in RedHat Israel, RHEV-M QE Network Team
Mobile: 054-5355725
IRC: mburman