There is no misuse when optional argument is not used. But hosted engine
uses the timeout parameter anyway so you can assume it is not a blocker for
us.
Martin
On Tue, Dec 19, 2017 at 12:56 PM, Martin Perina <mperina(a)redhat.com> wrote:
As Irit mentioned the provided reproduction steps are wrong (misuse
of the
code) and she posted correct example showing that jsonrpc code works as
expected. So Martin/Simone are you using somewhere in HE code the original
example that is misusing the client?
Thanks
Martin
On Tue, Dec 19, 2017 at 12:53 PM, Oved Ourfali <oourfali(a)redhat.com>
wrote:
> From the latest comment it doesn't seem like a blocker to me.
> Martin S. - your thoughts?
>
> On Tue, Dec 19, 2017 at 1:48 PM, Sandro Bonazzola <sbonazzo(a)redhat.com>
> wrote:
>
>> We have a proposed blocker for the release:
>> 1527155 <
https://bugzilla.redhat.com/show_bug.cgi?id=1527155> Infra vdsm
>> Bindings-API igoihman(a)redhat.com NEW jsonrpc reconnect logic does not
>> work and gets stuck
>> <
https://bugzilla.redhat.com/show_bug.cgi?id=1527155> urgent unspecified
>> ovirt-4.2.0 04:30:30
>>
>> Please review and either approve the blcoker or postpone to 4.2.1.
>> Thanks,
>>
>>
>> --
>>
>> SANDRO BONAZZOLA
>>
>> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
>>
>> Red Hat EMEA <
https://www.redhat.com/>
>> <
https://red.ht/sig>
>> TRIED. TESTED. TRUSTED. <
https://redhat.com/trusted>
>>
>>
>> _______________________________________________
>> Devel mailing list
>> Devel(a)ovirt.org
>>
http://lists.ovirt.org/mailman/listinfo/devel
>>
>
>
--
Martin Perina
Associate Manager, Software Engineering
Red Hat Czech s.r.o.