On Tue, Jul 12, 2016 at 10:12 AM, Francesco Romani <fromani(a)redhat.com>
wrote:
----- Original Message -----
> From: "Dan Kenigsberg" <danken(a)redhat.com>
> To: "Nadav Goldin" <ngoldin(a)redhat.com>, fromani(a)redhat.com
> Cc: "Eyal Edri" <eedri(a)redhat.com>, "Nir Soffer"
<nsoffer(a)redhat.com>,
"Yaniv Kaul" <ykaul(a)redhat.com>, "Martin
> Perina" <mperina(a)redhat.com>, "Tolik Litovsky"
<tlitovsk(a)redhat.com>,
"infra" <infra(a)ovirt.org>
> Sent: Monday, July 11, 2016 10:12:48 PM
> Subject: Re: Build failed in Jenkins: ovirt_master_system-tests #243
>
> On Thu, Jul 07, 2016 at 07:00:35PM +0300, Nadav Goldin wrote:
> > Seems like [1], as ovirt-srv19 has fresh new FC24 installation,
> > virtlogd is not enabled by default:
> > ● virtlogd.service - Virtual machine log manager
> > Loaded: loaded (/usr/lib/systemd/system/virtlogd.service; indirect;
> > vendor preset: disabled)
> > Active: inactive (dead)
> > Docs: man:virtlogd(8)
> >
http://libvirt.org
> > we can add it to puppet for now.
> >
> > [1]
https://bugzilla.redhat.com/show_bug.cgi?id=1290357
>
> Francesco, shouldn't vdsm require virtlogd explicitly?
Disclaimer: I didn't read yet the rest of the thread.
We choose not to, trying to prevent issues:
https://gerrit.ovirt.org/#/c/55189/1
Related-To:
https://bugzilla.redhat.com/show_bug.cgi?id=1318902
I thought and still do it's quite a mistake - if we think a feature of our
friends from libvirt is immature - we should tell them that, hopefully
accompanied by bugs.
I'd like to believe they don't enable features by default unless they
believe the features are mature and ready for general consumption. If
that's not the case, we should talk with them.
Y.
We want to reenable and require it in the near future:
https://bugzilla.redhat.com/show_bug.cgi?id=1321010
HTH,
--
Francesco Romani
RedHat Engineering Virtualization R & D
Phone: 8261328
IRC: fromani