<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jul 12, 2016 at 10:12 AM, Francesco Romani <span dir="ltr"><<a href="mailto:fromani@redhat.com" target="_blank">fromani@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
<br>
----- Original Message -----<br>
> From: "Dan Kenigsberg" <<a href="mailto:danken@redhat.com">danken@redhat.com</a>><br>
> To: "Nadav Goldin" <<a href="mailto:ngoldin@redhat.com">ngoldin@redhat.com</a>>, <a href="mailto:fromani@redhat.com">fromani@redhat.com</a><br>
> Cc: "Eyal Edri" <<a href="mailto:eedri@redhat.com">eedri@redhat.com</a>>, "Nir Soffer" <<a href="mailto:nsoffer@redhat.com">nsoffer@redhat.com</a>>, "Yaniv Kaul" <<a href="mailto:ykaul@redhat.com">ykaul@redhat.com</a>>, "Martin<br>
> Perina" <<a href="mailto:mperina@redhat.com">mperina@redhat.com</a>>, "Tolik Litovsky" <<a href="mailto:tlitovsk@redhat.com">tlitovsk@redhat.com</a>>, "infra" <<a href="mailto:infra@ovirt.org">infra@ovirt.org</a>><br>
> Sent: Monday, July 11, 2016 10:12:48 PM<br>
> Subject: Re: Build failed in Jenkins: ovirt_master_system-tests #243<br>
><br>
</span><span class="">> On Thu, Jul 07, 2016 at 07:00:35PM +0300, Nadav Goldin wrote:<br>
> > Seems like [1], as ovirt-srv19 has fresh new FC24 installation,<br>
> > virtlogd is not enabled by default:<br>
> > ● virtlogd.service - Virtual machine log manager<br>
> > Loaded: loaded (/usr/lib/systemd/system/virtlogd.service; indirect;<br>
> > vendor preset: disabled)<br>
> > Active: inactive (dead)<br>
> > Docs: man:virtlogd(8)<br>
> > <a href="http://libvirt.org" rel="noreferrer" target="_blank">http://libvirt.org</a><br>
> > we can add it to puppet for now.<br>
> ><br>
> > [1] <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1290357" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1290357</a><br>
><br>
> Francesco, shouldn't vdsm require virtlogd explicitly?<br>
<br>
</span>Disclaimer: I didn't read yet the rest of the thread.<br>
<br>
We choose not to, trying to prevent issues:<br>
<a href="https://gerrit.ovirt.org/#/c/55189/1" rel="noreferrer" target="_blank">https://gerrit.ovirt.org/#/c/55189/1</a><br>
Related-To: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1318902" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1318902</a></blockquote><div><br></div><div>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.</div><div>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.</div><div>Y.</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
We want to reenable and require it in the near future:<br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1321010" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1321010</a><br>
<br>
HTH,<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Francesco Romani<br>
RedHat Engineering Virtualization R & D<br>
Phone: 8261328<br>
IRC: fromani<br>
</font></span></blockquote></div><br></div></div>