2026621 – VLAN filtering cannot be configured with Intel X710

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2026621 - VLAN filtering cannot be configured with Intel X710

Summary: VLAN filtering cannot be configured with Intel X710

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 8
Classification:	Red Hat
Component:	nispor
Sub Component:
Version:	8.4
Hardware:	Unspecified
OS:	Unspecified
Priority:	urgent
Severity:	high
Target Milestone:	rc
Target Release:	8.6
Assignee:	Gris Ge
QA Contact:	Mingyu Shi
Docs Contact:
URL:
Whiteboard:
Duplicates (1):	2030197 (view as bug list)
Depends On:
Blocks:	2040316 2040317 2075200
TreeView+	depends on / blocked

Reported:	2021-11-25 10:58 UTC by Petr Horáček
Modified:	2022-05-10 14:32 UTC (History)
CC List:	10 users (show)
Fixed In Version:	nispor-1.2.3-1.el8
Doc Type:	No Doc Update
Doc Text:
Clone Of:
Clones:	2040316 2040317 2075200 (view as bug list)
Environment:
Last Closed:	2022-05-10 14:07:51 UTC
Type:	Bug
Target Upstream Version:
Embargoed:
Dependent Products:
Flags:	pm-rhel: mirror+

Attachments	(Terms of Use)
Diff of the failed configuration (2.84 KB, text/plain) 2021-11-25 10:58 UTC, Petr Horáček	no flags	Details
View All

Links
System	ID	Priority	Status	Summary	Last Updated
Github	nispor nispor pull 166	None	Merged	bridge vlan: Fix querying on i40e	2022-01-19 21:21:53 UTC
Red Hat Issue Tracker	RHELPLAN-103937	None	None	None	2021-11-25 11:01:06 UTC
Red Hat Knowledge Base (Solution)	6607691	None	None	None	2022-01-13 02:37:30 UTC
Red Hat Product Errata	RHEA-2022:1881	None	None	None	2022-05-10 14:07:58 UTC

Description Petr Horáček 2021-11-25 10:58:52 UTC

Created attachment 1843563 [details]
Diff of the failed configuration

Created attachment 1843563 [details]
Diff of the failed configuration

Description of problem:
When any VLAN filtering is configured on Intel X710, the configuration fails to get applied, with dmesg containing a number of following messages:
[79627.840049] i40e 0000:19:00.1: Error I40E_AQ_RC_ENOSPC adding RX filters on PF, promiscuous mode forced on

The odd part is that it happens even with a single VLAN trunk getting open, so it **should** not be a problem with lack of memory.


Version-Release number of selected component (if applicable):
RHEL 8.4
nmstate 1.0.2-14
NetworkManager in container, version 1.30.0-13.el8_4
NetworkManager on the host, version 1.30.0-10.el8_4


How reproducible:
Consistently on some PFs of the NIC. It always happens on the second one but did not happen on the third. While the second one had a wire connected, third one was disconnected.


Steps to Reproduce:
1. Get a host with Intel X710 NIC
2. Apply the following config:
    interfaces:
    - bridge:
        options:
          stp:
            enabled: false
        port:
        - name: eno2
          vlan:
            mode: trunk
            trunk-tags:
            - id: 1000
      ipv4:
        auto-dns: true
        dhcp: false
        enabled: false
      ipv6:
        enabled: false
      name: br1test
      state: up
      type: linux-bridge

Actual results:
Configuration fails, nmstate notices that requested VLANs were not applied. dmesg contains number of messages complaining about I40E_AQ_RC_ENOSPC. The number depends on how many IDs we atttemped to open.


Expected results:
We should be able to apply at least a limited numbed of trunk IDs on hardware that has offloading capability.


Additional info:

This reproduces even if vlan offloading gets disabled through ethtool:
rx-vlan-offload: off
tx-vlan-offload: off

Used NICs:
[root@cnv-qe-infra-32 /]# lspci  | grep 710
19:00.0 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 02)
19:00.1 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 02)
19:00.2 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 02)
19:00.3 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 02)

Comment 2 Fernando F. Mancera 2021-11-25 11:09:19 UTC

Debugging with nmcli and iproute2. I think this is probably a NM or kernel bug.

Comment 3 Petr Horáček 2021-11-25 11:25:07 UTC

After reboot of the host and trying again, the dmesg stopped appearing (is restart needed to clear the memory?). However, it still fails to configure the VLAN trunk.

Comment 6 Gris Ge 2021-12-13 08:51:36 UTC

Hi Petr,

This sounds like a kernel bug to me.
Can I close as duplication of bug 1959512 ?

Comment 7 Petr Horáček 2021-12-13 09:07:59 UTC

It's not clear that these two bugs are the same to me. Despite being in the same area, they are different. The on with Pensando caused the host to freeze. This Intel one just silently ignores the configuration. Marking it as a duplicate would be dangerous as we would skip the investigation and just assume it is already fixed. Could we move the BZ to kernel and let them evaluate it instead?

Comment 16 Gris Ge 2022-01-07 02:56:27 UTC

If nmcli can works, then nmstate should fix it or at lease workaround it.
I will take a look before 14 Jan 2022.

Comment 18 Gris Ge 2022-01-07 03:04:41 UTC

Acceptance criteria: Nmstate should support vlan filtering on intel X710(i40e driver).

Comment 19 Gris Ge 2022-01-07 04:43:23 UTC

Patch posted to https://github.com/nispor/nispor/pull/166

Backport scratch build:

RHEL 8.6: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=42249637
RHEL 8.5: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=42249613
RHEL 8.4: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=42249571


I have reproduce the problem and tested the 8.5 rpm on IBM s390x(ppc64le) server with Intel Corporation Ethernet Controller X710/X557-AT 10GBASE-T.

Comment 20 Gris Ge 2022-01-07 04:57:29 UTC

Hi nijin ashok,

Could you use above scratch rpm to test in your environment?

Thank you!

Comment 23 nijin ashok 2022-01-13 02:27:25 UTC

(In reply to Gris Ge from comment #20)
> Hi nijin ashok,
> 
> Could you use above scratch rpm to test in your environment?
> 
> Thank you!

Tested with the new build and nmstatectl was able to apply the VLANs successfully.

~~~
npc iface ens1f0 |grep -A8 vlans
Unhandled AF_SPEC_BRIDGE_INFO: 0 [2, 0]
Unhandled AF_SPEC_BRIDGE_INFO: 1 [1, 0]
Unhandled AF_SPEC_BRIDGE_INFO: 0 [2, 0]
Unhandled AF_SPEC_BRIDGE_INFO: 1 [1, 0]
    vlans:
      - vid: 1
        is_pvid: true
        is_egress_untagged: true
      - vid_range:
          - 100
          - 2412
        is_pvid: false
        is_egress_untagged: false
~~~

Comment 30 Gris Ge 2022-01-20 11:34:26 UTC

*** Bug 2030197 has been marked as a duplicate of this bug. ***

Comment 33 errata-xmlrpc 2022-05-10 14:07:51 UTC

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 (nispor bug fix and enhancement update), 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/RHEA-2022:1881

Note You need to log in before you can comment on or make changes to this bug.