[ovs-discuss] [openvswitch 2.11.0] testsuite: 2768 failed on s390x (big-endian)
Hi Test 2768 is consistently failing on s390x in Ubuntu development. Note that this is the only big-endian architecture we build for so I would suspect something endian-y as the root cause. Test log output: ## ## ## Summary of the failures. ## ## ## Failed tests: openvswitch 2.11.0 test suite test groups: NUM: FILE-NAME:LINE TEST-GROUP-NAME KEYWORDS 2768: ovn.at:12071 ovn -- ipam router ports ## -- ## ## Detailed failed tests. ## ## -- ## # -*- compilation -*- 2768. ovn.at:12071: testing ovn -- ipam router ports ... creating ovn-sb database creating ovn-nb database starting ovn-northd starting backup ovn-northd ../../tests/ovn.at:12083: ovn-nbctl get logical_router_port rop$i networks ../../tests/ovn.at:12083: ovn-nbctl get logical_router_port rop$i networks --- - 2019-03-01 11:43:30.807840002 + +++ /<>/_debian/tests/testsuite.dir/at-groups/2768/stdout 2019-03-01 11:43:30.800569938 + @@ -1,2 +1,2 @@ -["192.168.1.3/24"] +["192.168.1.2/24"] 2768. ovn.at:12071: 2768. ovn -- ipam router ports (ovn.at:12071): FAILED ( ovn.at:12083) Cheers James ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] ovs-vswitchd.service crashes
Hi Koukal I note that you're using the 4.18 kernel from Ubuntu; For Mellanox hardware offload I'd suggest you switch to using the hwe-edge kernel (5.3) as this is generally more mature for this (and other mlx5_core) feature - package name is 'linux-generic-hwe-18.04-edge'. On Thu, Nov 7, 2019 at 9:23 AM Koukal Petr wrote: > In case I turn off hw-offload with > ovs-vsctl set Open_vSwitch. other-config: hw-offload = false > then "ovs-vswitchd" is without collision. > > > Is it possible to reach someone who knows what to do with the offload > problem? > > Thank you for your help. > > Petr > On 11/6/19 6:48 PM, Ben Pfaff wrote: > > On Wed, Nov 06, 2019 at 01:59:36PM +0100, Koukal Petr wrote: > > The problem is the same even if hw-offload is off. > > I'm sending a log from ovs-vswitchd.log just after restarting the whole > openvswitch-switch. > Here you can see what happens before the assertion pops up. > > ethtool -K phys1-1 hw-tc-offload off > ethtool -K phys1-2 hw-tc-offload off > > This demonstrates turning off hardware offload at the ethtool level. > However, even with that, I believe that OVS will still try to use it if > OVS is configured for hardware offload. It looks like your OVS does > have hardware offload enabled. To turn it off, run: > > ovs-vsctl set Open_vSwitch . other-config:hw-offload=false > > Then restart OVS and see if it makes a difference. > > > Informace obsažené v této e-mailové zprávě a všech přiložených souborech > jsou důvěrné a jsou určeny pouze pro potřebu adresáta. Prosíme, abyste v > případě, že tento e-mail obdržíte omylem, neprodleně upozornili odesílatele > a tento e-mail odstranili z Vašeho systému. Pokud nejste zamýšleným > příjemcem, berte prosím na vědomí, že zveřejnění, kopírování, šíření či > přijetí jakéhokoliv opatření v souvislosti s obsahem této zprávy je > zakázáno a může být protiprávní. > > _ > > The information contained in this e-mail message and all attached files is > confidential and is intended solely for the use of the individual or entity > to whom they are addressed. Please notify the sender immediately if you > have received this e-mail by mistake and delete this e-mail from your > system. If you are not the intended recipient you are notified that > disclosing, copying, distributing or taking any action in reliance on the > contents of this information is prohibited and may be unlawful. > ___ > discuss mailing list > disc...@openvswitch.org > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss > ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] dpdk, netns and jumbo frames dropping packets
Bumping this thread as its been a while.
Anyone see any issues similar to this? We're still working around it with
the lower MTU.
On Tue, Jul 9, 2019 at 8:43 AM Liam Young wrote:
> Hi,
>
> I have a server which has an ovs bridge with a dpdk device attached
> for external network access and a network namespace attached via a tap
> device. Sending data out of the namespace fails if jumbo frames are
> enabled.
> Sending data into the namespace seems ok. Dropping the mtu of the tap
> device
> in the network namespace to 1500 also seems to fix the issue.
>
> I initially came across the issue in an OpenStack deployment and raised
> Bug #1833713 *1. However, I was able to reproduce the issue without
> OpenStack by manually creating the bridge etc *2.
>
> Any advice, tips or you-missed-this-step very gratefully received,
> Liam
>
> Below is my setup:
>
> Ubuntu: eoan
> DPDK pkg: 18.11.1-3
> OVS DPDK pkg: 2.11.0-0ubuntu2
> Kerenl: 5.0.0-20-generic
>
> root@node-licetus:~# ovs-vsctl show
> 523eab62-8d03-4445-a7ba-7570f5027ff6
> Bridge br-test
> Port "tap1"
> Interface "tap1"
> type: internal
> Port br-test
> Interface br-test
> type: internal
> Port "dpdk-nic1"
> Interface "dpdk-nic1"
> type: dpdk
> options: {dpdk-devargs=":03:00.0"}
> ovs_version: "2.11.0"
>
> root@node-licetus:~# ovs-vsctl get Interface dpdk-nic1 mtu
> 9000
>
> root@node-licetus:~# ip netns exec ns1 ip addr show tap1
> 12: tap1: mtu 9000 qdisc
> fq_codel state UNKNOWN group default qlen 1000
> link/ether 0a:dd:76:38:52:54 brd ff:ff:ff:ff:ff:ff
> inet 10.246.112.101/21 scope global tap1
>valid_lft forever preferred_lft forever
> inet6 fe80::8dd:76ff:fe38:5254/64 scope link
>valid_lft forever preferred_lft forever
>
> Using iperf to send data out of the netns fails:
>
> root@node-licetus:~# ip netns exec ns1 iperf -c 10.246.114.29
>
> Client connecting to 10.246.114.29, TCP port 5001
> TCP window size: 325 KByte (default)
>
> [ 3] local 10.246.112.101 port 51590 connected with 10.246.114.29 port 5001
> [ ID] Interval Transfer Bandwidth
> [ 3] 0.0-10.3 sec 323 KBytes 257 Kbits/sec
>
>
> root@node-hippalus:~# iperf -s -m
>
> Server listening on TCP port 5001
> TCP window size: 128 KByte (default)
>
> root@node-hippalus:~#
>
>
>
> *1 https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1833713
> *2 https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1833713/comments/7
> ___
> discuss mailing list
> disc...@openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] [ovs-dev] OVS 2.12/2.13 compilation on Ubuntu Bionic
On Tue, Jul 7, 2020 at 8:39 AM Maciej Jozefczyk wrote:
> Hello,
>
> Thank you for your responses!
>
> Is there any reason not to use the in-tree openvswitch kernel module
>> provided in the Ubuntu kernels? Ubuntu stopped shipping DKMS modules as
>> part of OVS quite a long time ago as the openvswitch module in the kernel
>> is well maintained and generally up-to-date - and also to avoid this type
>> of breaking change.
>>
>
> Yes. QoS for OVN wasn't really working before until the OVN team started
> using OVS meter actions. Those type of actions are not working properly
> with OVS kernel module shipped by Ubuntu Bionic (up to kernel 4.18.0 [1]),
> so to test this functionality in Neutron upstream gates we compile the
> module from OVS source.
>
As an alternative you could use the HWE kernels provided for Ubuntu 18.04
LTS:
linux-image-generic-hwe-18.04-edge (5.4)
linux-image-generic-hwe-18.04 (5.3)
however that may mean that the default images used for testing in openinfra
might need to be updated to use the latest kernel versions
> This patch is actually on branch-2.12 and branch-2.13.
>> The only thing that is missing is a new stable release (tags).
>> We're going to release new stable versions on all previous branches soon.
>
>
> That is great news. Thank You!
>
> Maciej
>
> On Mon, Jul 6, 2020 at 7:58 PM Ilya Maximets wrote:
>
>> On 6/29/20 8:45 PM, Gregory Rose wrote:
>> >
>> >
>> > On 6/26/2020 4:57 AM, Maciej Jozefczyk wrote:
>> >> Hello!
>> >>
>> >> I would like to kindly ask You if there is a possibility to cherry-pick
>> >> patch [1] to stable branches OVS 2.12, OVS 2.13 and release new tags
>> for it?
>> >>
>> >> Without this patch we're now unable to compile OVS 2.12 in OpenStack
>> >> Neutron stable releases CI, because it recently started to fail on
>> Ubuntu
>> >> Bionic with an error:
>> >>
>> >> 2020-06-24 14:50:13.975917 | primary |
>> >> /opt/stack/new/ovs/datapath/linux/geneve.c: In function
>> >> ‘geneve_get_v6_dst’:
>> >> 2020-06-24 14:50:13.975993 | primary |
>> >> /opt/stack/new/ovs/datapath/linux/geneve.c:966:15: error: ‘const
>> >> struct ipv6_stub’ has no member named ‘ipv6_dst_lookup’
>> >> 2020-06-24 14:50:13.976026 | primary | if
>> >> (ipv6_stub->ipv6_dst_lookup(geneve->net, gs6->sock->sk, &dst, fl6)) {
>> >> 2020-06-24 14:50:13.976049 | primary |^
>> >> 2020-06-24 14:50:14.010809 | primary | scripts/Makefile.build:285:
>> >> recipe for target '/opt/stack/new/ovs/datapath/linux/geneve.o' failed
>> >>
>> >> The same happens for OVN 2.13. For now this blocks your CI pipelines.
>> >>
>> >> Can I ask You to backport this patch?
>>
>> This patch is actually on branch-2.12 and branch-2.13.
>> The only thing that is missing is a new stable release (tags).
>> We're going to release new stable versions on all previous branches soon.
>>
>> Best regards, Ilya Maximets.
>>
>> >>
>> >> Thanks,
>> >> Maciej
>> >>
>> >> [1]
>> >>
>> https://github.com/openvswitch/ovs/commit/5519e384f6a17f564fef4c5eb39e471e16c77235
>> >>
>> >>
>> >> ___
>> >> discuss mailing list
>> >> disc...@openvswitch.org
>> >> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
>> >>
>> >
>> > Adding OVS Dev list where maybe the maintainers might see this sooner.
>> >
>> > - Greg
>>
>>
>
> --
> Best regards,
> Maciej Józefczyk
> ___
> discuss mailing list
> disc...@openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] [openvswitch 2.8.0 dpdk] testsuite: 1211 1212 1213 1214 1215 1217 1218 1219 1220 1221 1222 1224 1225 1226 2338 failed
On Wed, 9 Aug 2017 at 00:08 Ben Pfaff wrote: > On Tue, Aug 08, 2017 at 04:26:38PM +, Darrell Ball wrote: > > > > > > From: on behalf of James Page < > james.p...@ubuntu.com> > > Date: Tuesday, August 8, 2017 at 2:49 AM > > To: "b...@openvswitch.org" > > Subject: [ovs-discuss] [openvswitch 2.8.0 dpdk] testsuite: 1211 1212 > 1213 1214 1215 1217 1218 1219 1220 1221 1222 1224 1225 1226 2338 failed > > > > Hi > > > > I'm cutting builds from branch-2.8 in preparation for the ovs 2.8.0 > release for Ubuntu; we build and test two sets of binaries - a vanilla one > and one with dpdk enabled. > > > > I see test failures on all of the "ofproto-dpif - conntrack" tests with > the DPDK build and with the ovn ACL test (see attached logs). Vanilla > build is fine. > > > > James > > > > These are generic tests and should not be run with-dpdk set. > > If you run these tests --with-dpdk, some tests will consider the packets > coming an actual dpdk interface, which they are not. > > In this case, the packets will be marked with a bad checksum. > > All of the tests in the testsuite should always pass, or be skipped, > regardless of configuration, so if some of the tests are inappropriate > for a given configuration then they need AT_SKIP_IF([...]) to ensure > that they get skipped. > Glad to hear that - as part of the vanilla and DPDK binary builds, we run the complete test suite with both sets of binaries; the smaller the sauce we have to apply in the execution of the tests for the DPDK build the better! Cheers James ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
