[ovirt-devel] Can't join vdsm(4.17.0-390.gita3163f3.el7.x86_64) to Cluster 3.6

[ybronhei]

On 02/09/2015 08:35 AM, Oved Ourfali wrote:
>
> On Feb 9, 2015 9:31 AM, Sandro Bonazzola <sbonazzo at 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 at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/devel


-- 
Yaniv Bronhaim.