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

Bug 2109123

Summary: Bond CNI: balance-alb: No ping between 2 pods
Product: OpenShift Container Platform Reporter: elevin
Component: NetworkingAssignee: Marcin Mirecki <mmirecki>
Networking sub component: multus QA Contact: elevin
Status: CLOSED WONTFIX Docs Contact:
Severity: unspecified    
Priority: unspecified 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:05 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-20 13:02:38 UTC
Description of problem:
4: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether d2:54:96:09:16:4b brd ff:ff:ff:ff:ff:ff
    inet 192.168.100.1/24 brd 192.168.100.255 scope global bond0
       valid_lft forever preferred_lft forever
    inet6 fe80::d054:96ff:fe09:164b/64 scope link 
       valid_lft forever preferred_lft forever
1895: net1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
    link/ether d2:54:96:09:16:4b brd ff:ff:ff:ff:ff:ff
1984: net2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
    link/ether d2:54:96:09:16:4b brd ff:ff:ff:ff:ff:ff permaddr 3e:80:21:d3:13:32
sh-4.4# ping 192.168.100.2
PING 192.168.100.2 (192.168.100.2) 56(84) bytes of data.
^C
--- 192.168.100.2 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2046ms


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

How reproducible:
50%

Steps to Reproduce:
1.Create 2 SRiovNetworkNodePolicy with Intel nics 
2.Create 2 SriovNetwork with trust
3.Create 2 Bond NADs with balance-alb mode and mtu 1500
4.Configure non LACP LAGs on a switch
5. Create 2 pods with bond (server and client)
6.Send from one pod (client) to another one (server) over the switch

Actual results:
--- 192.168.100.2 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2046ms

Expected results:
no packet loos

Additional info:
Server pod doesn't answer on ARP request
If send ping from Server to Client, everything will work

Comment 1 Marcin Mirecki 2022-09-20 12:14:38 UTC
*** Bug 2037214 has been marked as a duplicate of this bug. ***

Comment 2 Carlos Goncalves 2022-11-14 14:53:05 UTC
Closing this as WONTFIX because...
1. ALB 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.