Red Hat Bugzilla – Bug 1578590
[OVS] [qede] Got ERR when configuring OVS-dpdk with qede NIC
Last modified: 2018-06-21 09:37:18 EDT
Description of problem: [OVS] [qede] Got ERR when configuring OVS-dpdk with qede NIC 2018-05-15T23:29:57.396Z|00170|dpdk|ERR|[qede_ucast_filter:681(85:00.0:dpdk-port-1)]Unicast MAC is already added with vlan = 0, vni = 0 2018-05-15T23:29:57.396Z|00171|dpdk|ERR|[qede_mac_int_ops:816(85:00.0:dpdk-port-1)]MAC filter failed, rc = -17, op = 1 [root@netqe9 jhsiao]# vs 5d023537-fac3-46fe-9af4-cee010d6bc24 Bridge "ovsbr0" Port "dpdk-11" Interface "dpdk-11" type: dpdk options: {dpdk-devargs="0000:85:00.1", n_rxq="2"} Port "ovsbr0" Interface "ovsbr0" type: internal Port "dpdk-10" Interface "dpdk-10" type: dpdk options: {dpdk-devargs="0000:85:00.0", n_rxq="2"} ovs_version: "2.9.0" Version-Release number of selected component (if applicable): [root@netqe9 jhsiao]# uname -a Linux netqe9.knqe.lab.eng.bos.redhat.com 3.10.0-862.el7.x86_64 #1 SMP Wed Mar 21 18:14:51 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux [root@netqe9 jhsiao]# rpm -q openvswitch openvswitch-2.9.0-36.el7fdp.x86_64 How reproducible: Reproducible Steps to Reproduce: 1. Have a qede installed: FastLinQ QL45212H 25GbE Adapter 2. Config a OVS-dpdk with qede 3. Check /var/log/openvswitch/ovs-vswitchd.log Actual results: Got ERRs Expected results: Should not get ERRs Additional info:
NOTE: The network traffic has been flowing well over qede dpdk interfaces. So, not sure what will be the impact of the the ERR.
Created attachment 1437751 [details] Potential fix
Hi Rasesh, If we provide the src rpm could you build us a test kit with your fix to check it?
Hi Christian - sure, we can provide a custom test kit.
The test build provided with fix, it was tested by Jean and it was verified issue is fixed. We have submitted the fix to dpdk.org and marked for inclusion in stable. It has been accepted upstream. Thanks! -Rasesh
The fix of this BZ has been verified with OVS 2.9.0-47.
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, 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-2018:1962