Hi,
thanks for the exhaustive answer again.
But is the mom release all?
are the related changes to the
guest agent and to vdsm also released?
in which version?
Also I think this:
http://rhn.redhat.com/errata/RHEA-2014-0064.html
is incorrect, as it states that this is fixed
in the mom release, but it isn't.
it relies on swap information from guest-agent
which also needs an upgrade (if the guest has swap
configured).
I think there is some lack of documentation
around this.
Which version of vdsm and guest agent do you
need to use this new mom?
Am 22.01.2014 17:52, schrieb Adam Litke:
On 22/01/14 03:12 -0500, Doron Fediuck wrote:
>
>
> ----- Original Message -----
>> From: "Sven Kieske" <S.Kieske(a)mittwald.de>
>> To: "Users(a)ovirt.org List" <Users(a)ovirt.org>
>> Sent: Tuesday, January 21, 2014 6:45:10 PM
>> Subject: [Users] no new mom for ovirt?
>>
>> Hi,
>>
>> I just checked this BZ:
>>
https://bugzilla.redhat.com/show_bug.cgi?id=1025845
>>
>> This is closed for RedHat but afaik not for upstream.
>>
>> It mentions the fixed mom version:
>> mom-0.3.2-8.el6ev
>>
>> but on
resources.ovirt.org I find just older versions
>> like
>>
http://resources.ovirt.org/releases/3.4.0-alpha/rpm/EL/6/noarch/mom-0.3.2...
>>
>>
>> so downstream (payed) red hat has newer versions than upstream
>>
>> how can that be? Or am I looking in the wrong repo?
>> Should this not be hosted on
ovirt.org repo?
Hi Sven! Thanks for bringing this up. You have stumbled upon our
completely broken mom build process in oVirt. Part of the problem
stems from the fact that MOM is a standalone package (available in
upstream Fedora) which is being rebuilt by oVirt. The Fedora releases
have typically been much slower than the oVirt releases (and different
people are doing each). Here's what we are doing to fix the issues:
- Fix the MOM build system (merged)
- Create branches in the MOM repo for ovirt releases (in progress)
- I will be taking responsibility for oVirt releases of MOM in
addition to the Fedora package itself.
These changes should lead to a normalized release process for MOM and
ensure that built packages for all supported oVirt releases will be
made available on
resources.ovirt.org.
Up until very recently, all MOM development has been done in a single
branch. As a workaround for your issue you can build your own rpm
from git (use the v0.3.2-stable tag) or grab this [1] nightly build.
[1]
http://resources.ovirt.org/releases/nightly/rpm/EL/6Server/noarch/mom-0.3...
Sorry for all of the confusion!
--
Mit freundlichen Grüßen / Regards
Sven Kieske
Systemadministrator
Mittwald CM Service GmbH & Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +49-5772-293-100
F: +49-5772-293-333
https://www.mittwald.de
Geschäftsführer: Robert Meyer
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen