[ovirt-devel] ioprocess 0.14.0 released

[Michal Skrivanek]

On Dec 3, 2014, at 10:49 , Yeela Kaplan <ykaplan at redhat.com> wrote:

> 
> 
> ----- Original Message -----
>> From: "Michal Skrivanek" <michal.skrivanek at redhat.com>
>> To: "Saggi Mizrahi" <smizrahi at redhat.com>, "Oved Ourfali" <ovedo at redhat.com>
>> Cc: "Martyn Taylor" <mtaylor at redhat.com>, devel at ovirt.org
>> Sent: Wednesday, December 3, 2014 11:30:34 AM
>> Subject: Re: [ovirt-devel] ioprocess 0.14.0 released
>> 
>> 
>> On Oct 23, 2014, at 10:06 , Saggi Mizrahi <smizrahi at redhat.com> wrote:
>> 
>>> 
>>> 
>>> ----- Original Message -----
>>>> From: "Michal Skrivanek" <michal.skrivanek at redhat.com>
>>>> To: "Saggi Mizrahi" <smizrahi at redhat.com>
>>>> Cc: devel at ovirt.org, "Martyn Taylor" <mtaylor at redhat.com>
>>>> Sent: Wednesday, October 22, 2014 10:55:34 AM
>>>> Subject: Re: [ovirt-devel] ioprocess 0.14.0 released
>>>> 
>>>> 
>>>> On Oct 21, 2014, at 10:59 , Saggi Mizrahi <smizrahi at redhat.com> wrote:
>>>> 
>>>>> ioprocess 0.14.0 has been tagged and released.
>>>>> 
>>>>> The changelog includes:
>>>>> - python-bindings: IOProcess objects can be collected by the GC
>>>>> - python-bindings: Slave processes can optionally be collected
>>>>>                 by zombie reaper
>>>>> 
>>>>> It's recommended that everyone upgrade to the latest version.
>>>> 
>>>> does this remove the annoying debug level messages in vdsm.log?
>>>> or some other patch already addressed that?
>>> Long long time ago. We added the TRACE level that is only
>>> used during iprocess development.
>>> 
>>> * Sun Jul 20 2014 Saggi Mizrahi <smizrahi at redhat.com> 0.6.1-1
>>> - Reduced logging even for debug level
>> 
>> well, I still see that in *latest* 3.5 on QE systems. It's really annoying…
>> might it be because of upgrades?
>> Oved, IMHO it needs to be fixed/clarified ASAP, the logs are useless...
>> 
> 
> If QE has latest 3.5 then they should have ioprocess-0.14 installed,
> if that's the case and there's still too much logging then the issue should be checked.

Ha! indeed it was not the case. The system as somehow missing many updates, including ioprocess.
It should have probably been enforced…but I agree if one does a proper yum update it should work (I didn't try it yet;-)

Thanks,
michal

> 
>> Thanks,
>> michal
>> 
>>>> 
>>>> Thanks,
>>>> michal
>>>> 
>>>>> 
>>>>> Please test and give karma:
>>>>> https://admin.fedoraproject.org/updates/search/ioprocess-0.14.0
>>>>> 
>>>>> Good day.
>>>>> _______________________________________________
>>>>> Devel mailing list
>>>>> Devel at ovirt.org
>>>>> http://lists.ovirt.org/mailman/listinfo/devel
>>>> 
>>>> 
>> 
>> _______________________________________________
>> Devel mailing list
>> Devel at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/devel
>>