Bug 1936417

Summary:	ovs-tcpdump on a dpdk bond doesn't set the proper mtu on the mirror port
Product:	Red Hat Enterprise Linux Fast Datapath	Reporter:	Takashi Kajinami <tkajinam>
Component:	openvswitch	Assignee:	Aaron Conole <aconole>
openvswitch sub component:	daemons and tools	QA Contact:	Hekai Wang <hewang>
Status:	VERIFIED ---	Docs Contact:
Severity:	medium
Priority:	unspecified	CC:	ctrautma, fleitner, jhsiao, mleitner
Version:	RHEL 7.7
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openvswitch2.17-2.17.0-59.el8fdp	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2152451 (view as bug list)		Environment:
Last Closed:		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:
Bug Depends On:
Bug Blocks:	2152451

Description Takashi Kajinami 2021-03-08 12:52:46 UTC

Description of problem:

Currently when ovs-tcpdump create a mirror port, it adjust mtu of the mirror port based on the mtu of the target port[1].
 https://mail.openvswitch.org/pipermail/ovs-dev/2017-February/329030.html

However this adjustment doesn't work for dpdk-bond. We need to manually adjust mtu of the mirror port if physical interfaces of the bond has MTU larger than the default (1,500).

Version-Release number of selected component (if applicable):
openvswitch-test-2.9.0-110.el7fdp.noarch and RHEL7.7

How reproducible:
Always

Steps to Reproduce:
1. Create a dpdk bond and set mtu 9000 on physical interfaces
2. Take packet capture on the dpdk bond port by ovs-tcpdump

Actual results:
The mirror port has mtu 9,000 and packets are captured properly

Expected results:
The mirror port has mtu 1,500 (default) and no packets are captured

Additional info:

Comment 2 Aaron Conole 2022-11-02 14:15:14 UTC

https://lists.linuxfoundation.org/pipermail/ovs-dev/2022-October/398267.html

This was accepted and will be resolved with openvswitch2.17-2.17.0-59.el8fdp

Comment 4 Marcelo Ricardo Leitner 2023-05-03 20:36:21 UTC

Did this one fall through the cracks of the Errata maybe?