Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2106906

Summary: Bond CNI: Traffic doesn't work with balance-tlb bond mode
Product: OpenShift Container Platform Reporter: elevin
Component: NetworkingAssignee: Marcin Mirecki <mmirecki>
Networking sub component: multus QA Contact: zhaozhanqi <zzhao>
Status: CLOSED WONTFIX Docs Contact:
Severity: medium    
Priority: medium CC: cgoncalves
Version: 4.11   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-14 14:53:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description elevin 2022-07-13 20:22:25 UTC
Description of problem:
No traffic
=============
Client:

259: net2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1450 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
    link/ether 86:47:a0:be:0c:2e brd ff:ff:ff:ff:ff:ff permaddr 32:5c:c4:f6:0e:6c
3: eth0@if331: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1400 qdisc noqueue state UP mode DEFAULT group default 
    link/ether 0a:58:0a:83:01:fb brd ff:ff:ff:ff:ff:ff link-netnsid 0
4: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1450 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 86:47:a0:be:0c:2e brd ff:ff:ff:ff:ff:ff
210: net1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1450 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
    link/ether 86:47:a0:be:0c:2e brd ff:ff:ff:ff:ff:ff

sh-4.4# cat /sys/class/net/bond0/bonding/mode 
balance-tlb 5
sh-4.4# ping 192.168.100.2 -c3
PING 192.168.100.2 (192.168.100.2) 56(84) bytes of data.
From 192.168.100.1 icmp_seq=1 Destination Host Unreachable
From 192.168.100.1 icmp_seq=2 Destination Host Unreachable
From 192.168.100.1 icmp_seq=3 Destination Host Unreachable
===============================================================
server:

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked v1), capture size 262144 bytes
20:16:40.794944 ARP, Request who-has bondpod-2 tell 192.168.100.1, length 46
20:16:41.839160 ARP, Request who-has bondpod-2 tell 192.168.100.1, length 46
20:16:42.863150 ARP, Request who-has bondpod-2 tell 192.168.100.1, length 46

sh-4.4# ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
3: eth0@if327: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1400 qdisc noqueue state UP mode DEFAULT group default 
    link/ether 0a:58:0a:80:02:0b brd ff:ff:ff:ff:ff:ff link-netnsid 0
4: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1450 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 52:64:c8:a0:0a:20 brd ff:ff:ff:ff:ff:ff
295: net2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1450 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
    link/ether 52:64:c8:a0:0a:20 brd ff:ff:ff:ff:ff:ff permaddr ce:d4:3e:71:dc:63
213: net1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1450 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
    link/ether 52:64:c8:a0:0a:20 brd ff:ff:ff:ff:ff:ff

sh-4.4# cat /sys/class/net/bond0/bonding/mode
balance-tlb 5


Version-Release number of selected component (if applicable):
4.11.0-rc.0

How reproducible:
100%

Steps to Reproduce:
1.Apply sriovnodes configs
2.Apply sriovnetwork configs
3. Apply NAD with tlb bond mode configs
4. Configure non LACP LAGs on a swtich
5. Create client and server pods with bonds
6. Ping from client to server

Actual results:
Traffic failed

Expected results:
Traffic passed

Additional info:

Comment 1 Carlos Goncalves 2022-11-14 14:53:55 UTC
Closing this as WONTFIX because...
1. TLB bond mode is not supported and there are currently no plans to support it in Bond CNI.
2. Red Hat is migrating the bug reporting system to Jira (issues.redhat.com) and teams were asked to groom open BZ bugs.