On Tue, Nov 06, 2018 at 12:01:17PM +0530, Numan Siddique wrote:
> On Tue, Nov 6, 2018 at 2:22 AM Ben Pfaff <[email protected]> wrote:
> 
> > On Tue, Nov 06, 2018 at 01:40:48AM +0530, Numan Siddique wrote:
> > > On Mon, Nov 5, 2018, 8:43 PM Ben Pfaff <[email protected] wrote:
> > >
> > > > On Fri, Nov 02, 2018 at 05:11:01PM +0530, [email protected] wrote:
> > > > > From: Numan Siddique <[email protected]>
> > > > >
> > > > > When 'make check' is called by the mock rpm build (which disables
> > > > networking),
> > > > > the test "ovn-nbctl: LBs - daemon" fails when it runs the command
> > > > > "ovn-nbctl lb-add lb0 30.0.0.1a 192.168.10.10:80,192.168.10.20:80".
> > > > ovn-nbctl
> > > > > extracts the vip by calling the socket util function
> > > > 'inet_parse_active()',
> > > > > and this function blocks when libunbound function ub_resolve() is
> > called
> > > > > further down. ub_resolve() is a blocking function without timeout and
> > > > all the
> > > > > ovs/ovn utilities use this function.
> > > > >
> > > > > As reported by Timothy Redaelli, the issue can also be reproduced by
> > > > running
> > > > > the below commands
> > > > >
> > > > > $ sudo unshare -mn -- sh -c 'ip addr add dev lo 127.0.0.1 && \
> > > > >   mount --bind /dev/null /etc/resolv.conf && runuser $SUDO_USER'
> > > > > $ make sandbox SANDBOXFLAGS="--ovn"
> > > > > $ ovn-nbctl -vsocket_util:off lb-add lb0 30.0.0.1a \
> > > > >   192.168.10.10:80,192.168.10.20:80
> > > > >
> > > > > To address this issue, this patch adds a new bool argument
> > > > 'resolve_host' to
> > > > > the function inet_parse_active() to resolve the host only if it is
> > > > 'true'.
> > > > >
> > > > > ovn-nbctl/ovn-northd will pass 'false' when it calls this function to
> > > > parse
> > > > > the load balancer values.
> > > > >
> > > > > Reported-by: Timothy Redaelli <[email protected]>
> > > > > Reported-at: https://bugzilla.redhat.com/show_bug.cgi?id=1641672
> > > > > Signed-off-by: Numan Siddique <[email protected]>
> > > >
> > > > Thanks, applied to master.
> > > >
> > >
> > > Thanks. Since the issue is also seen with 2.10, is it possible to
> > backport
> > > to 2.10 branch.
> >
> > There's a patch conflict for branch-2.10, so would you mind posting a
> > manual backport?
> >
> 
> Sure. I posted here  - https://patchwork.ozlabs.org/patch/993517/

Thanks, applied.
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to