Re: [ovirt-devel] Can't join vdsm(4.17.0-390.gita3163f3.el7.x86_64) to Cluster 3.6
On Feb 11, 2015 10:49 PM, Michael Burman <mburman@redhat.com> wrote:
Hello Yaniv and all!
So i did this: I tried to install clean rhel7.1 host with the right libvirt version(libvirt-1.2.8-16.el7.x86_64,vdsm-4.17.0-394.gitb237397.el7.x86_64) and failed to join this host under 3.6 cluster. Host red-vds2.qa.lab.tlv.redhat.com is compatible with versions (3.0,3.1,3.2,3.3,3.4,3.5) and cannot join Cluster mb3.6 which is set to version 3.6. After failing i checked the /usr/share/vdsm/dsaversion.py and saw that: version_info = { 'version_name': version_name, 'software_version': software_version, 'software_revision': software_revision, 'supportedENGINEs': ['3.0', '3.1', '3.2', '3.3', '3.4', '3.5'], 'supportedProtocols': ['2.2', '2.3'], 'clusterLevels': ['3.0', '3.1', '3.2', '3.3', '3.4', '3.5'],
So i added the 3.6 for cluster levels and engine support lines, restarted vdsm and finally managed to join my rhel7.1 host to 3.6 Cluster.
All of this means that rhel7.1 hosts with vdsm 4.17.0 and libvirt version -libvirt-1.2.8-16.el7.x86_64 are still not supported by default for 3.6 clusters and dsaversion.py file must be edited manually in order to join to cluster 3.6. I guess this must be changed.
+1 on that one.
Best regards, Michael B
----- Original Message ----- From: "Michael Burman" <mburman@redhat.com> To: "ybronhei" <ybronhei@redhat.com> Cc: devel@ovirt.org, infra@ovirt.org Sent: Monday, February 9, 2015 10:50:28 AM Subject: Re: [ovirt-devel] Can't join vdsm(4.17.0-390.gita3163f3.el7.x86_64) to Cluster 3.6
Thank you all!
Ok, so how can i get this right libvirt version for rhel7? not7.1 and without any dependencies issues?? I want to join rhel7 host, with the right libvirt version to 3.6 cluster..is it possible?
Michael B
----- Original Message ----- From: "ybronhei" <ybronhei@redhat.com> To: "Oved Ourfali" <oourfali@redhat.com>, "Sandro Bonazzola" <sbonazzo@redhat.com>, "Dan Kenigsberg" <danken@redhat.com> Cc: infra@ovirt.org, devel@ovirt.org, "Michael Burman" <mburman@redhat.com> Sent: Monday, February 9, 2015 10:03:56 AM Subject: Re: [ovirt-devel] Can't join vdsm(4.17.0-390.gita3163f3.el7.x86_64) to Cluster 3.6
On 02/09/2015 08:35 AM, Oved Ourfali wrote:
On Feb 9, 2015 9:31 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Il 08/02/2015 16:15, Michael Burman ha scritto:
Hi everyone!
Is any one knows when it will be possible to join vdsm-4.17.0 to 3.6 Cluster?? I know that the libvirt version is not supported, but isn't should be? even if it's rhel7..?
I changed the /usr/share/vdsm/dsaversion.py file to: 'supportedENGINEs': ['3.0', '3.1', '3.2', '3.3', '3.4', '3.5', '3.6'], 'supportedProtocols': ['2.2', '2.3'], 'clusterLevels': ['3.0', '3.1', '3.2', '3.3', '3.4', '3.5', '3.6'],
But caps.py is still: if not hasattr(libvirt, 'VIR_MIGRATE_AUTO_CONVERGE'): return _dropVersion('3.6', 'VIR_MIGRATE_AUTO_CONVERGE not found in libvirt,' ' support for clusterLevel >= 3.6 is disabled.' ' For Fedora 20 users, please consider upgrading' ' libvirt from the virt-preview repository')
if not hasattr(libvirt, 'VIR_MIGRATE_COMPRESSED'): return _dropVersion('3.6', 'VIR_MIGRATE_COMPRESSED not found in libvirt,' ' support for clusterLevel >= 3.6 is disabled.' ' For Fedora 20 users, please consider upgrading' ' libvirt from the virt-preview repository')
libvirt is still disabled for 3.6 clusters...
I already tried to rebuild from fedora(with Sandro appreciated help), but had a lot of issues dependencies.
I'm running on- ovirt-engine-3.6.0-0.0.master.20150206122208.gitd429375.el6.noarch vdsm-4.17.0-390.gita3163f3.el7.x86_64 libvirt-1.1.1-29.el7_0.7.x86_64
I would like to know if and when it will be possible to join rhel7 host(vdsm-4.17.0) to Cluster 3.6?
Moving to devel list, not really an infra issue.
Yaniv, you had a patch for that, but it was abandoned. Why?
because we don't need it- i explained there the cluster check is only after the supportedVDSMVersion does not catch. we failed to add the host to the cluster because the libvirt version . as it is now, with the right versions, you should be able to add vdsm 4.17 to lastest engine regardless the cluster level
Best regards,
Michael B
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Yaniv Bronhaim.
-- Michael Burman Intern in RedHat Israel, RHEV-M QE Network Team
Mobile: 054-5355725 IRC: mburman _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Michael Burman Intern in RedHat Israel, RHEV-M QE Network Team
Mobile: 054-5355725 IRC: mburman _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
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. ----- Original Message ----- From: "Oved Ourfali" <oourfali@redhat.com> To: "Michael Burman" <mburman@redhat.com> Cc: infra@ovirt.org, devel@ovirt.org, "ybronhei" <ybronhei@redhat.com> Sent: Thursday, February 12, 2015 7:13:13 AM Subject: Re: [ovirt-devel] Can't join vdsm(4.17.0-390.gita3163f3.el7.x86_64) to Cluster 3.6 On Feb 11, 2015 10:49 PM, Michael Burman <mburman@redhat.com> wrote:
Hello Yaniv and all!
So i did this: I tried to install clean rhel7.1 host with the right libvirt version(libvirt-1.2.8-16.el7.x86_64,vdsm-4.17.0-394.gitb237397.el7.x86_64) and failed to join this host under 3.6 cluster. Host red-vds2.qa.lab.tlv.redhat.com is compatible with versions (3.0,3.1,3.2,3.3,3.4,3.5) and cannot join Cluster mb3.6 which is set to version 3.6. After failing i checked the /usr/share/vdsm/dsaversion.py and saw that: version_info = { 'version_name': version_name, 'software_version': software_version, 'software_revision': software_revision, 'supportedENGINEs': ['3.0', '3.1', '3.2', '3.3', '3.4', '3.5'], 'supportedProtocols': ['2.2', '2.3'], 'clusterLevels': ['3.0', '3.1', '3.2', '3.3', '3.4', '3.5'],
So i added the 3.6 for cluster levels and engine support lines, restarted vdsm and finally managed to join my rhel7.1 host to 3.6 Cluster.
All of this means that rhel7.1 hosts with vdsm 4.17.0 and libvirt version -libvirt-1.2.8-16.el7.x86_64 are still not supported by default for 3.6 clusters and dsaversion.py file must be edited manually in order to join to cluster 3.6. I guess this must be changed.
+1 on that one.
Best regards, Michael B
----- Original Message ----- From: "Michael Burman" <mburman@redhat.com> To: "ybronhei" <ybronhei@redhat.com> Cc: devel@ovirt.org, infra@ovirt.org Sent: Monday, February 9, 2015 10:50:28 AM Subject: Re: [ovirt-devel] Can't join vdsm(4.17.0-390.gita3163f3.el7.x86_64) to Cluster 3.6
Thank you all!
Ok, so how can i get this right libvirt version for rhel7? not7.1 and without any dependencies issues?? I want to join rhel7 host, with the right libvirt version to 3.6 cluster..is it possible?
Michael B
----- Original Message ----- From: "ybronhei" <ybronhei@redhat.com> To: "Oved Ourfali" <oourfali@redhat.com>, "Sandro Bonazzola" <sbonazzo@redhat.com>, "Dan Kenigsberg" <danken@redhat.com> Cc: infra@ovirt.org, devel@ovirt.org, "Michael Burman" <mburman@redhat.com> Sent: Monday, February 9, 2015 10:03:56 AM Subject: Re: [ovirt-devel] Can't join vdsm(4.17.0-390.gita3163f3.el7.x86_64) to Cluster 3.6
On 02/09/2015 08:35 AM, Oved Ourfali wrote:
On Feb 9, 2015 9:31 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Il 08/02/2015 16:15, Michael Burman ha scritto:
Hi everyone!
Is any one knows when it will be possible to join vdsm-4.17.0 to 3.6 Cluster?? I know that the libvirt version is not supported, but isn't should be? even if it's rhel7..?
I changed the /usr/share/vdsm/dsaversion.py file to: 'supportedENGINEs': ['3.0', '3.1', '3.2', '3.3', '3.4', '3.5', '3.6'], 'supportedProtocols': ['2.2', '2.3'], 'clusterLevels': ['3.0', '3.1', '3.2', '3.3', '3.4', '3.5', '3.6'],
But caps.py is still: if not hasattr(libvirt, 'VIR_MIGRATE_AUTO_CONVERGE'): return _dropVersion('3.6', 'VIR_MIGRATE_AUTO_CONVERGE not found in libvirt,' ' support for clusterLevel >= 3.6 is disabled.' ' For Fedora 20 users, please consider upgrading' ' libvirt from the virt-preview repository')
if not hasattr(libvirt, 'VIR_MIGRATE_COMPRESSED'): return _dropVersion('3.6', 'VIR_MIGRATE_COMPRESSED not found in libvirt,' ' support for clusterLevel >= 3.6 is disabled.' ' For Fedora 20 users, please consider upgrading' ' libvirt from the virt-preview repository')
libvirt is still disabled for 3.6 clusters...
I already tried to rebuild from fedora(with Sandro appreciated help), but had a lot of issues dependencies.
I'm running on- ovirt-engine-3.6.0-0.0.master.20150206122208.gitd429375.el6.noarch vdsm-4.17.0-390.gita3163f3.el7.x86_64 libvirt-1.1.1-29.el7_0.7.x86_64
I would like to know if and when it will be possible to join rhel7 host(vdsm-4.17.0) to Cluster 3.6?
Moving to devel list, not really an infra issue.
Yaniv, you had a patch for that, but it was abandoned. Why?
because we don't need it- i explained there the cluster check is only after the supportedVDSMVersion does not catch. we failed to add the host to the cluster because the libvirt version . as it is now, with the right versions, you should be able to add vdsm 4.17 to lastest engine regardless the cluster level
Best regards,
Michael B
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Yaniv Bronhaim.
-- Michael Burman Intern in RedHat Israel, RHEV-M QE Network Team
Mobile: 054-5355725 IRC: mburman _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Michael Burman Intern in RedHat Israel, RHEV-M QE Network Team
Mobile: 054-5355725 IRC: mburman _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Michael Burman Intern in RedHat Israel, RHEV-M QE Network Team Mobile: 054-5355725 IRC: mburman
----- Original Message -----
From: "Michael Burman" <mburman@redhat.com> To: "Oved Ourfali" <oourfali@redhat.com>, "ybronhei" <ybronhei@redhat.com> Cc: devel@ovirt.org, infra@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
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@redhat.com> To: "Michael Burman" <mburman@redhat.com> Cc: "Oved Ourfali" <oourfali@redhat.com>, "ybronhei" <ybronhei@redhat.com>, devel@ovirt.org, infra@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@redhat.com> To: "Oved Ourfali" <oourfali@redhat.com>, "ybronhei" <ybronhei@redhat.com> Cc: devel@ovirt.org, infra@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
participants (3)
-
Francesco Romani -
Michael Burman -
Oved Ourfali