** Changed in: charm-neutron-openvswitch
Milestone: 20.08 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833713
Title:
Metadata is broken with dpdk bonding, jumbo frames and metadata
I think this is related to bug 1831935 - where the recommendation is
that the use of veth is disabled in DPDK deployments to avoid the
checksumming issues - see the 'ovs-use-veth' configuration option. This
is a breaking change but the charm should stop you doing anything that
will break things.
bug 1832021 looks very similar and some changes landed across releases
this month to disable checksum calcs for veth interfaces when in use
with DPDK (stein/train/ussuri/master branches).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Marking as field-high as this now affects a live cloud, and the
workaround (lowering the MTU within the qdhcp namespaces) isn't fully
persistent.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833713
** Changed in: charm-neutron-openvswitch
Milestone: 20.05 => 20.08
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833713
Title:
Metadata is broken with dpdk bonding, jumbo frames and metadata
Does anybody know if upstream responded elsewhere?
https://mail.openvswitch.org/pipermail/ovs-discuss/2019-July/048997.html
shows no thread reply.
Wouldn't it be best to open a bug instead?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to
Does anybody know if upstream responded elsewhere?
https://mail.openvswitch.org/pipermail/ovs-discuss/2019-July/048997.html
shows no thread reply.
Wouldn't it be best to open a bug instead?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: charm-neutron-openvswitch
Milestone: 20.01 => 20.05
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833713
Title:
Metadata is broken with dpdk bonding, jumbo frames and metadata
** Changed in: charm-neutron-openvswitch
Milestone: 19.10 => 20.01
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833713
Title:
Metadata is broken with dpdk bonding, jumbo frames and metadata
I'm hitting this bug in a client installation, Bionic / Queens. Just spent a
few hours debugging and in the end came to exactly the same tests and
conclusion.
Using DPDK, using bond for dpdk, using isolated metadata (as this is
provider only networks). I *can* send data to the netns up to 9000
I'm marking this bug as triaged - we can reproduce the issue outside of
openstack.
** Changed in: charm-neutron-openvswitch
Status: New => Triaged
** Changed in: dpdk (Ubuntu)
Status: New => Triaged
** Changed in: charm-neutron-openvswitch
Importance: Undecided => High
**
No reply yet in the ML.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833713
Title:
Metadata is broken with dpdk bonding, jumbo frames and metadata from
qdhcp
To manage notifications about this
No reply yet in the ML.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to dpdk in Ubuntu.
https://bugs.launchpad.net/bugs/1833713
Title:
Metadata is broken with dpdk bonding, jumbo frames and metadata from
qdhcp
To manage notifications
Hi Christian,
Thanks for your comments. I'm sure you spotted it but just to make it
clear, the issue occurs with bonded and unbonded dpdk interfaces. I've emailed
upstream here *1.
Thanks
Liam
*1 https://mail.openvswitch.org/pipermail/ovs-discuss/2019-July/048997.html
--
You received
Hi Liam,
all I can say about this area is that I heard from several others that MTU+Bond
was very broken in the past - I haven't heard an update on that for a while.
Thanks for trying 18.11.2 in that regard.
I've read through the case about but nothing obvious came up for me to
try or fix.
I
** Changed in: dpdk (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833713
Title:
Metadata is broken with dpdk bonding, jumbo frames and metadata from
qdhcp
Ubuntu: eoan
DPDK pkg: 18.11.1-3
OVS DPDK pkg: 2.11.0-0ubuntu2
Kerenl: 5.0.0-20-generic
If a server has an ovs bridge with a dpdk device for external
network access and a network namespace attached then sending data out of
the namespace fails if jumbo frames are enabled.
Setup:
Ubuntu: eoan
DPDK pkg: 18.11.1-3
OVS DPDK pkg: 2.11.0-0ubuntu2
Kerenl: 5.0.0-20-generic
If two servers each have an ovs bridge with a dpdk device for external
network access and a network namespace attached then communication
between taps in the namespaces fails if jumbo frames are enabled. If
At some point when I was attempting to simplify the test case I
dropped setting the mtu on the dpdk devices via ovs so the above test is
invalid. I've marked the bug against dpdk as invalid while I redo the
tests.
** Changed in: dpdk (Ubuntu)
Status: New => Invalid
--
You received this
Given the above I'm am going to mark this as affecting the dpdk package
rather than the charm
** Also affects: dpdk (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
20 matches
Mail list logo
