-
Bug
-
Resolution: Done
-
Major
-
None
-
4.10.z
-
Important
-
No
-
CNF Network Sprint 244
-
1
-
False
-
-
-
Description of problem:
Unable to send traffic using the testcmd tool over a Bond sriov interface. However, the ping and curl commands can pass traffic.
Version-Release number of selected component (if applicable):
How reproducible:
Easily
Steps to Reproduce:
1. Deploy OCP 4.10.67 2. Run cnf-gotest sriov bond active active bond test. 3. Access pods and send traffic
Actual results:
/var/lib/jenkins/workspace/ocp-cnf-core-tests/cnf-gotests/test/network/sriov/netsriovhelper/netsriovhelper.go:213 Traffic failed Unexpected error: <exec.CodeExitError>: { Err: <*errors.errorString | 0xc0008f3d30>{ s: "command terminated with exit code 1", }, Code: 1, } command terminated with exit code 1 occurred /var/lib/jenkins/workspace/ocp-cnf-core-tests/cnf-gotests/test/network/sriov/netsriovhelper/sriov_bond_helper.go:177
Expected results:
To pass traffic without an error
Additional info:
When passing traffic with icmp or curl I see traffic arriving to the otherside. 05:09:38.767038 IP dns-default.openshift-dns.svc.cluster.local.domain > testpod-jg72m.42067: 59530 NXDomain 0/1/1 (177) 05:09:43.794164 ARP, Request who-has _gateway tell testpod-jg72m, length 28 05:09:43.794902 ARP, Reply _gateway is-at 0a:58:0a:83:00:01 (oui Unknown), length 28 06:06:26.546493 IP6 testpod-jg72m > ff02::2: ICMP6, router solicitation, length 16 [root@testpod-skzx8 /]# ping 192.168.100.1 PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data. 64 bytes from 192.168.100.1: icmp_seq=1 ttl=64 time=0.183 ms 64 bytes from 192.168.100.1: icmp_seq=2 ttl=64 time=0.128 ms 64 bytes from 192.168.100.1: icmp_seq=3 ttl=64 time=0.111 ms 64 bytes from 192.168.100.1: icmp_seq=4 ttl=64 time=0.107 ms testcmd command connectivity test failedUDP test failed[root@testpod-skzx8 /]# testcmd -interface bond0 -server 192.168.100.1 -protocol udp -port 6001 UDP PING 192.168.100.1 1450(1478) bytes of data. write udp4 192.168.100.2:52129->192.168.100.1:6001: write: message too long write udp4 192.168.100.2:52129->192.168.100.1:6001: write: message too long [root@testpod-jg72m /]# testcmd -interface bond0 -listen -protocol udp -port 6001