Hi,
what about older but still supported ovirt version?
I ask for all the 3.3.x people, we could need the bugfixes
from mom, too.
the host side packages are all supposed to be backward compatible, so
once this is fixed for latets vdsm/mom/etc., you should be able to use
this with ovirt 3.2 engine as well, etc.?
Am 24.01.2014 11:44, schrieb Dan Kenigsberg:
> On Thu, Jan 23, 2014 at 04:23:48PM -0500, Adam Litke wrote:
>> On 23/01/14 23:02 +0200, Itamar Heim wrote:
>>> On 01/23/2014 08:04 PM, Adam Litke wrote:
>>>> On 23/01/14 10:43 -0300, Federico Alberto Sayd wrote:
>>>>> On 22/01/14 21:32, Dan Kenigsberg wrote:
>>>>>> On Wed, Jan 22, 2014 at 01:57:35PM -0300, Federico Alberto Sayd
wrote:
>>>>>>> On 22/01/14 12:13, Dan Kenigsberg wrote:
>>>>>> <snip>
>>>>>>
>>>>>>> The supervdsm.log whith the lines logged yesterday:
>>>>>>>
>>>>>>>
http://pastebin.com/kpXrRd2w
>>>>>>>
>>>>>> On an unrelated matter: this log includes
>>>>>>
>>>>>> MainProcess|PolicyEngine::DEBUG::2014-01-21
>>>>>>
13:13:41,187::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper) call
>>>>>> ksmTune with ({},) {}
>>>>>> MainProcess|PolicyEngine::DEBUG::2014-01-21
>>>>>>
13:13:41,188::supervdsmServer::102::SuperVdsm.ServerCallback::(wrapper)
>>>>>> return ksmTune with None
>>>>>> MainProcess|PolicyEngine::DEBUG::2014-01-21
>>>>>>
13:13:51,220::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper) call
>>>>>> ksmTune with ({},) {}
>>>>>> MainProcess|PolicyEngine::DEBUG::2014-01-21
>>>>>>
13:13:51,220::supervdsmServer::102::SuperVdsm.ServerCallback::(wrapper)
>>>>>> return ksmTune with None
>>>>>>
>>>>>> spam every 10 seconds. Federico, which version of mom do you
have
>>>>>> installed? I
>>>>>> thought we have solved a similar issue in the past.
>>>>>>
>>>>>>
>>>>> mom-0.3.2-6.el6.noarch
>>>>
>>>> This is the upstream version of mom which (sadly) is far too old and
>>>> is missing a bunch of features. For Fedora, we are building master
>>>> and releasing versions like mom-0.3.2-20140120.gitfd877c5.fc20 [1]
>>>> which have lots of ovirt-specific fixes applied.
>>>>
>>>> The fix is to have someone rebuild the mom RPM for el6 since the last
>>>> refresh happened on August 13 (!). For now, please try to upgrade to
>>>> this build of master [2].
>>>
>>> any reason we don't build it via jenkins to
resources.ovirt.org
>>> like other rpms?
>>
>> Yes, because (up until now) the mom build system was not compatible
>> with other oVirt projects. That was fixed this week [1] so now we can
>> release proper RPMs into the oVirt repositories. Next I want to do a
>> MOM version bump and synchronize the official Fedora packages with
>> what we have in oVirt.
>>
>> Any opinion on whether we should adopt the current MOM master (build
>> system rewrite) this late in the 3.4 release process? If so, I will
>> work with Sandro to make sure that rc1 has it updated. Othewise, we
>> can do that for 3.4.1.
>
> Currently 3.4 beta includes
>
http://resources.ovirt.org/releases/beta/rpm/EL/6/noarch/mom-0.3.2-3.el6....
> which is sorely outdated, as you say. We should fix this as soon as
> possible. Branching one week too late is a small price to pay, imo.
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/users
>
>
>