[Users] Testday aftermath

Joop jvdwege at xs4all.nl
Sun Feb 3 18:59:11 UTC 2013


Vijay Bellur wrote:
> On 02/01/2013 07:38 PM, Kanagaraj wrote:
>> On 02/01/2013 06:47 PM, Joop wrote:
>>> Shireesh Anjal wrote:
>>>> On 02/01/2013 05:13 PM, noc wrote:
>>>>> On 1-2-2013 11:07, Kanagaraj wrote:
>>>>>> Hi Joop,
>>>>>>
>>>>>>  Looks like the problem is because of the glusterfs version you are
>>>>>> using. vdsm could not parse the output from gluster.
>>>>>>
>>>>>>  Can you update the glusterfs to
>>>>>> http://bits.gluster.org/pub/gluster/glusterfs/v3.4.0qa7/x86_64/ and
>>>>>> check it out?
>>>>> How??
>>>>>
>>>>> I tried adding this repo but but yum says that there are no updates
>>>>> available, atleast yesterday it did.
>>>>>
>>>>> [gluster-nieuw]
>>>>> name=GlusterFS
>>>>> baseurl=http://bits.gluster.org/pub/gluster/glusterfs/stage/
>>>>> gpgcheck=0
>>>>> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-Gluster
>>>>> enabled=1
>>>>>
>>>>> My yumfoo isn't that good so I don't know how to force it. Besides I
>>>>> tried through yum localinstall but it will revert when yum update is
>>>>> run. It looks like it thinks that 3.3.1 is newer than 3.4
>>>>
>>>> The problem is that, released glusterfs rpms in fedora repository are
>>>> of the form 3.3.1-8, whereas the ones from above QA release are
>>>> v3.4.0qa7. I think because of the "v" before 3.4, these are
>>>> considered as lower version, and by default yum picks up the rpms
>>>> from fedora repository.
>>>>
>>> The 'v' is 99.9% the culprit. I had 3.4.0qa6 before I wiped and just
>>> had a look that folder and repo doesn't have the 'v' in front of it.
>>>
>> Thats correct.
>>
>> [kanagaraj at localhost ~]$ rpmdev-vercmp glusterfs-3.3.1-8.fc18.x86_64
>> glusterfs-v3.4.0qa7-1.el6.x86_64
>> glusterfs-3.3.1-8.fc18.x86_64 > glusterfs-v3.4.0qa7-1.el6.x86_64
>>
>>> Is there someone on this list that has the 'powers' to change that ??
>>>
>>
>> [Adding Vijay]
>>
>
> 3.4.0qa8 is available now. Can you please check with that?
>
> Thanks,
> Vijay
I can report back that 3.4.0qa8 does work. oVirt also picked up on the 
volumes that I created but didn't show up in the interface. Could start 
them an will test if they are fully usable.

Thanks for the quick respons.

Joop




More information about the Users mailing list