<div dir="ltr"><div>In my opinion this issue is protocol agnostic. We may want to have a retry logic<br></div><div>to make sure client can "talk" to vdsm.<br><br></div><div>It seems that we could have this logic in the client code (disabled by default) and<br></div><div>client code could enable it if needed.<br></div><div><div><div><div><div><br><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 18, 2016 at 11:25 AM, Oved Ourfali <span dir="ltr"><<a href="mailto:oourfali@redhat.com" target="_blank">oourfali@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><p dir="ltr">Discuss it with the infra guys and I'm sure you'll get the reasons, and will figure out a solution together. <br>
</p>
<div class="gmail_extra"><br><div class="gmail_quote">On Nov 18, 2016 12:21 PM, "Martin Sivak" <<a href="mailto:msivak@redhat.com" target="_blank">msivak@redhat.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">What about making vdsm ready to answer connections when it returns to<br>
systemd instead? I hate workarounds and this always worked fine.<br></blockquote></div></div></blockquote><div><br></div><div>I am not so sure whether it will be so simple to do it. Recovery can take some time<br></div><div>and during this time vdsm is not functional. Interesting issue found [1].<br><br><br>[1] <a href="https://bugzilla.redhat.com/1396183">https://bugzilla.redhat.com/1396183</a><br></div><div><br> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Martin<br>
<br>
On Fri, Nov 18, 2016 at 11:13 AM, Oved Ourfali <<a href="mailto:oourfali@redhat.com" target="_blank">oourfali@redhat.com</a>> wrote:<br>
> Seems like a race regardless of the protocol.<br>
> Should you add a retry?<br>
><br>
><br>
> On Nov 18, 2016 11:52 AM, "Martin Sivak" <<a href="mailto:msivak@redhat.com" target="_blank">msivak@redhat.com</a>> wrote:<br>
>><br>
>> Yes, because VDSM is supposed to be up (there is systemd dependency).<br>
>> This always worked fine with xml-rpc.<br>
>><br>
>> Martin<br>
>><br>
>> On Fri, Nov 18, 2016 at 10:14 AM, Nir Soffer <<a href="mailto:nsoffer@redhat.com" target="_blank">nsoffer@redhat.com</a>> wrote:<br>
>> > On Fri, Nov 18, 2016 at 10:45 AM, Martin Sivak <<a href="mailto:msivak@redhat.com" target="_blank">msivak@redhat.com</a>><br>
>> > wrote:<br>
>> >> This happens because MOM can't connect to VDSM and so it quits.<br>
>> ><br>
>> > So mom try once to connect and if the connection fails it quits?<br>
>> ><br>
>> >> We<br>
>> >> discussed it on the mailinglist<br>
>> >><br>
>> >><br>
>> >> <a href="https://lists.fedoraproject.org/archives/list/vdsm-devel@lists.fedorahosted.org/thread/MZ7UJUWO5KFRDJJDNXX7VIYU5PWSXF62/" rel="noreferrer" target="_blank">https://lists.fedoraproject.or<wbr>g/archives/list/vdsm-devel@lis<wbr>ts.fedorahosted.org/thread/MZ7<wbr>UJUWO5KFRDJJDNXX7VIYU5PWSXF62/</a><br>
>> >> <a href="http://lists.ovirt.org/pipermail/devel/2016-November/014101.html" rel="noreferrer" target="_blank">http://lists.ovirt.org/piperma<wbr>il/devel/2016-November/014101.<wbr>html</a><br>
>> >><br>
>> >> This issue never happened with XML-RPC.<br>
>> >><br>
>> >> Shira reported it as<br>
>> >> <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1393012" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/sh<wbr>ow_bug.cgi?id=1393012</a><br>
>> >><br>
>> >> Martin<br>
>> >><br>
>> >> On Thu, Nov 17, 2016 at 7:42 PM, Yaniv Kaul <<a href="mailto:ykaul@redhat.com" target="_blank">ykaul@redhat.com</a>> wrote:<br>
>> >>> I've recently seen, including now on Master, the following warnings:<br>
>> >>> Nov 17 13:33:25 lago-basic-suite-master-host0 systemd[1]: Started MOM<br>
>> >>> instance configured for VDSM purposes.<br>
>> >>> Nov 17 13:33:25 lago-basic-suite-master-host0 systemd[1]: Starting MOM<br>
>> >>> instance configured for VDSM purposes...<br>
>> >>> Nov 17 13:33:35 lago-basic-suite-master-host0 vdsm[2012]: vdsm MOM<br>
>> >>> WARN MOM<br>
>> >>> not available, Policy could not be set.<br>
>> >>> Nov 17 13:33:39 lago-basic-suite-master-host0 vdsm[2012]: vdsm MOM<br>
>> >>> WARN MOM<br>
>> >>> not available.<br>
>> >>> Nov 17 13:33:39 lago-basic-suite-master-host0 vdsm[2012]: vdsm MOM<br>
>> >>> WARN MOM<br>
>> >>> not available, KSM stats will be missing.<br>
>> >>> Nov 17 13:33:55 lago-basic-suite-master-host0 vdsm[2012]: vdsm MOM<br>
>> >>> WARN MOM<br>
>> >>> not available.<br>
>> >>> Nov 17 13:33:55 lago-basic-suite-master-host0 vdsm[2012]: vdsm MOM<br>
>> >>> WARN MOM<br>
>> >>> not available, KSM stats will be missing.<br>
>> >>> Nov 17 13:34:10 lago-basic-suite-master-host0 vdsm[2012]: vdsm MOM<br>
>> >>> WARN MOM<br>
>> >>> not available.<br>
>> >>> Nov 17 13:34:10 lago-basic-suite-master-host0 vdsm[2012]: vdsm MOM<br>
>> >>> WARN MOM<br>
>> >>> not available, KSM stats will be missing.<br>
>> >>> Nov 17 13:34:26 lago-basic-suite-master-host0 vdsm[2012]: vdsm MOM<br>
>> >>> WARN MOM<br>
>> >>> not available.<br>
>> >>> Nov 17 13:34:26 lago-basic-suite-master-host0 vdsm[2012]: vdsm MOM<br>
>> >>> WARN MOM<br>
>> >>> not available, KSM stats will be missing.<br>
>> >>> Nov 17 13:34:42 lago-basic-suite-master-host0 vdsm[2012]: vdsm MOM<br>
>> >>> WARN MOM<br>
>> >>> not available.<br>
>> >>> Nov 17 13:34:42 lago-basic-suite-master-host0 vdsm[2012]: vdsm MOM<br>
>> >>> WARN MOM<br>
>> >>> not available, KSM stats will be missing.<br>
>> >>> Nov 17 13:34:57 lago-basic-suite-master-host0 vdsm[2012]: vdsm MOM<br>
>> >>> WARN MOM<br>
>> >>> not available.<br>
>> >>> Nov 17 13:34:57 lago-basic-suite-master-host0 vdsm[2012]: vdsm MOM<br>
>> >>> WARN MOM<br>
>> >>> not available, KSM stats will be missing.<br>
>> >>> Nov 17 13:35:12 lago-basic-suite-master-host0 vdsm[2012]: vdsm MOM<br>
>> >>> WARN MOM<br>
>> >>> not available.<br>
>> >>><br>
>> >>><br>
>> >>><br>
>> >>> Any ideas what this is and why?<br>
>> >>><br>
>> >>> ______________________________<wbr>_________________<br>
>> >>> Devel mailing list<br>
>> >>> <a href="mailto:Devel@ovirt.org" target="_blank">Devel@ovirt.org</a><br>
>> >>> <a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/devel</a><br>
>> >> ______________________________<wbr>_________________<br>
>> >> Devel mailing list<br>
>> >> <a href="mailto:Devel@ovirt.org" target="_blank">Devel@ovirt.org</a><br>
>> >> <a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/devel</a><br>
>> ______________________________<wbr>_________________<br>
>> Devel mailing list<br>
>> <a href="mailto:Devel@ovirt.org" target="_blank">Devel@ovirt.org</a><br>
>> <a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/devel</a><br>
>><br>
>><br>
><br>
</blockquote></div></div>
</blockquote></div><br></div></div></div></div></div></div></div>