RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1578889 - TCP retransmissions on host-VM connections using OVS bridge leading to timeouts
Summary: TCP retransmissions on host-VM connections using OVS bridge leading to timeouts
Keywords:
Status: CLOSED DUPLICATE of bug 1572983
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: openvswitch
Version: 7.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Eric Garver
QA Contact: ovs-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-16 14:42 UTC by Daniel Alvarez Sanchez
Modified: 2018-05-24 13:25 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-24 13:25:31 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1771500 0 None None None 2018-05-16 14:42:26 UTC

Description Daniel Alvarez Sanchez 2018-05-16 14:42:26 UTC 
Description of problem:
While running OpenStack tests we see that a connection from the host to a guess VM in the same node is very slow due to lots of retransmissions apparently because of wrong checksums.

The layout is as follows:

host -> br-ex (OVS bridge) -> tap device -> VM

The 3-way handshake is very fast and the connection establishes normally.
However, when data is sent from the VM to the host (using netcat in my tests), we can see that data packets gets retransmitted by the VM and they reach the host with wrong checksum. Only until the checksum is correct (it eventually is correct after a few retranmissions), the host will send the ACK to the packet.

Version-Release number of selected component (if applicable):
Kernel 3.10.0-862.2.3.el7.x86_64
OVS: openvswitch-2.9.0-3.el7.x86_64

This didn't happen with CentOS kernel 7.4

How reproducible:
100%


Additional info:

This doesn't happen if instead from trying to reach the VM from the host we create an OVS internal port, put it in the namespace and repeat the process. In this case, the checksums are correct and the connection works as expected.

More details at https://bugs.launchpad.net/packstack/+bug/1771500
Comment 2 Daniel Alvarez Sanchez 2018-05-16 14:51:53 UTC 
Looks like this is not failing neither on D/S CI nor TripleO CI jobs where they seem to attach a physical interface to br-ex. In packstack/devstack, jobs simply do the following:

$ sudo ip link set br-ex up
$ sudo ip route add 172.24.4.0/24 dev br-ex
$ sudo ip addr add 172.24.4.1/24 dev br-ex

And this is where we see the wrong checksums and retransmissions.
Comment 6 Daniel Alvarez Sanchez 2018-05-17 16:41:19 UTC 
(In reply to Daniel Alvarez Sanchez from comment #2)
> Looks like this is not failing neither on D/S CI nor TripleO CI jobs where
> they seem to attach a physical interface to br-ex. In packstack/devstack,
> jobs simply do the following:
> 
> $ sudo ip link set br-ex up
> $ sudo ip route add 172.24.4.0/24 dev br-ex
> $ sudo ip addr add 172.24.4.1/24 dev br-ex
> 
> And this is where we see the wrong checksums and retransmissions.

I've repeated the tests in a failing setup attaching a phys interface to br-ex and it still fails. My guess is that this is not failing on Tripleo CI / DS because tempest is being run from a separate node (ie. starting connections to the FIP from a different node) so probably checksums are getting fixed somewhere in the way?
Comment 10 Eric Garver 2018-05-23 15:47:56 UTC 
@fwestpha pointed me to bug 1572983. A new kernel with the nf_reset() fix works with my reproducer [0]. Basically, the skb's ctinfo was not being scrubbed properly.

Please retest after a kernel with the fix for bug 1572983 is available.

[0] http://git.engineering.redhat.com/git/users/egarver/ovs.git/commit/?h=bz1578889&id=364cecd5ef101ad5fd512c83e2ef686f192419d6
Comment 12 Daniel Alvarez Sanchez 2018-05-24 10:09:06 UTC 
(In reply to Eric Garver from comment #10)
> @fwestpha pointed me to bug 1572983. A new kernel with the nf_reset() fix
> works with my reproducer [0]. Basically, the skb's ctinfo was not being
> scrubbed properly.
> 
> Please retest after a kernel with the fix for bug 1572983 is available.
> 
> [0]
> http://git.engineering.redhat.com/git/users/egarver/ovs.git/commit/
> ?h=bz1578889&id=364cecd5ef101ad5fd512c83e2ef686f192419d6

Timothy and I have tried  3.10.0-891.el7.test.x86_64 on OpenStack and I can confirm that it fixes the issue. However, we're not using network namespaces at all in OVN so not sure if it's this what fixes it or any other patch.
Comment 13 Eric Garver 2018-05-24 13:25:31 UTC 
(In reply to Daniel Alvarez Sanchez from comment #12)
> (In reply to Eric Garver from comment #10)
> > @fwestpha pointed me to bug 1572983. A new kernel with the nf_reset() fix
> > works with my reproducer [0]. Basically, the skb's ctinfo was not being
> > scrubbed properly.
> > 
> > Please retest after a kernel with the fix for bug 1572983 is available.
> > 
> > [0]
> > http://git.engineering.redhat.com/git/users/egarver/ovs.git/commit/
> > ?h=bz1578889&id=364cecd5ef101ad5fd512c83e2ef686f192419d6
> 
> Timothy and I have tried  3.10.0-891.el7.test.x86_64 on OpenStack and I can
> confirm that it fixes the issue. However, we're not using network namespaces
> at all in OVN so not sure if it's this what fixes it or any other patch.

Thanks for confirming. I will mark this as a duplicate then.

FWIW, nf_reset() is called for various reasons. One of which occurs on OVS internal port RX.

*** This bug has been marked as a duplicate of bug 1572983 ***
Note You need to log in before you can comment on or make changes to this bug.