Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
The FDP team is no longer accepting new bugs in Bugzilla. Please report your issues under FDP project in Jira. Thanks.

Bug 2236359

Summary: LB skip_snat improperly applied with affinity_timeout
Product: Red Hat Enterprise Linux Fast Datapath Reporter: OVN Bot <ovn-bot>
Component: ovn23.06Assignee: Ales Musil <amusil>
Status: CLOSED ERRATA QA Contact: ying xu <yinxu>
Severity: medium Docs Contact:
Priority: unspecified    
Version: FDP 23.KCC: amusil, ctrautma, jiji, jishi, sdodson
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovn23.06-23.06.1-5.el9fdp Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-10-18 00:27:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OVN Bot 2023-08-31 04:05:12 UTC 
This is an automatically-generated clone of issue https://bugzilla.redhat.com/show_bug.cgi?id=2224260
Comment 3 ying xu 2023-09-21 02:01:23 UTC 
I can reproduce it on version:
# rpm -qa|grep ovn
ovn23.06-23.06.0-56.el9fdp.x86_64
ovn23.06-central-23.06.0-56.el9fdp.x86_64
ovn23.06-host-23.06.0-56.el9fdp.x86_64

#ip netns exec bar1 python3 -m http.server 8080 &' (Expected 0, got 0)
Serving HTTP on :: port 8080 (http://[::]:8080/) ...
#ip netns exec foo1 curl 192.168.1.100:1234
::ffff:192.168.2.1 - - [20/Sep/2023 21:54:29] "GET / HTTP/1.1" 200 -   ---------------the return ip is 192.168.2.1,should be 192.168.1.1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Directory listing for /</title>
</head>
<body>
<h1>Directory listing for /</h1>
<hr>
<ul>
<li><a href="arping.log">arping.log</a></li>
<li><a href="bar1.log">bar1.log</a></li>
<li><a href="fip0.pcap">fip0.pcap</a></li>
<li><a href="fip1.pcap">fip1.pcap</a></li>
<li><a href="lr0.pcap">lr0.pcap</a></li>
<li><a href="lr1.pcap">lr1.pcap</a></li>
<li><a href="ls0.pcap">ls0.pcap</a></li>
<li><a href="ls1.pcap">ls1.pcap</a></li>
<li><a href="Makefile">Makefile</a></li>
<li><a href="PURPOSE">PURPOSE</a></li>
<li><a href="runtest.sh">runtest.sh</a></li>
<li><a href="runtest1.sh">runtest1.sh</a></li>
<li><a href="server0.log">server0.log</a></li>
<li><a href="server1.log">server1.log</a></li>
<li><a href="testinfo.desc">testinfo.desc</a></li>
<li><a href="trace.log">trace.log</a></li>
</ul>
<hr>
</body>
</html>

verified on version:
ovn23.06-23.06.1-11.el9fdp.x86_64
ovn23.06-central-23.06.1-11.el9fdp.x86_64
ovn23.06-host-23.06.1-11.el9fdp.x86_64

[root@dell-per730-57 load_balance]# ip netns exec bar1 python3 -m http.server 8080 &
[3] 64774
[root@dell-per730-57 load_balance]# Serving HTTP on :: port 8080 (http://[::]:8080/) ...

[root@dell-per730-57 load_balance]# ip netns exec foo1 curl 192.168.1.100:1234
::ffff:192.168.1.2 - - [20/Sep/2023 21:49:42] "GET / HTTP/1.1" 200 -             ---------------this is the correct return ip
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Directory listing for /</title>
</head>
<body>
<h1>Directory listing for /</h1>
<hr>
<ul>
<li><a href="bar1.log">bar1.log</a></li>
<li><a href="Makefile">Makefile</a></li>
<li><a href="ovs_ixgbe.log">ovs_ixgbe.log</a></li>
<li><a href="PURPOSE">PURPOSE</a></li>
<li><a href="runtest.sh">runtest.sh</a></li>
<li><a href="testinfo.desc">testinfo.desc</a></li>
</ul>
<hr>
</body>
</html>
Comment 5 errata-xmlrpc 2023-10-18 00:27:29 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (ovn23.06 bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:5823