"dev" <[email protected]> wrote on 07/25/2016 07:58:03 AM:
> From: Ryan Moats/Omaha/IBM@IBMUS > To: Zong Kai LI <[email protected]> > Cc: [email protected] > Date: 07/25/2016 07:58 AM > Subject: Re: [ovs-dev] [PATCH] [PATCH v1] ovs python: add set type > forfrom_python > Sent by: "dev" <[email protected]> > > "dev" <[email protected]> wrote on 07/19/2016 03:59:39 AM: > > > From: Zong Kai LI <[email protected]> > > To: [email protected] > > Date: 07/19/2016 04:03 AM > > Subject: [ovs-dev] [PATCH] [PATCH v1] ovs python: add set type for > from_python > > Sent by: "dev" <[email protected]> > > > > In method from_python, when parameter 'value' is in list type or tuple > > type, it will process per each element in 'value'. And indeed, it just > > needs a iterable sequence here, no matter it's a list or tuple. > > So set type should be considered too, it's also a basic, common iterable > > sequence type from python. > > > > Signed-off-by: Zong Kai LI <[email protected]> > > From Richard Theis <[email protected]>: > > This patch is need to avoid the revert [1] in networking-ovn. Without > this patch or the revert, networking-ovn is experiencing the bug > described in [2]. > > Acked-by: Richard Theis <[email protected]> > > [1] http://review.openstack.org/344078 > [2] https://bugs.launchpad.net/networking-ovn/+bug/1605573 > > Ryan Moats I ran the test reported in [2] to confirm the bug. After applying the revert [1], the reported bug was fixed. That is, I was able to ssh between my instances with the router setup described in [2]. I also confirmed that the networks field was properly set for the logical router ports. I then removed the revert [1] and applied this patch. This patch also worked. Tested-by: Richard Theis <[email protected]> > > > _______________________________________________ > dev mailing list > [email protected] > http://openvswitch.org/mailman/listinfo/dev _______________________________________________ dev mailing list [email protected] http://openvswitch.org/mailman/listinfo/dev
