Bug 2075200
| Summary: | VLAN filtering cannot be configured with Intel X710 | ||
|---|---|---|---|
| Product: | Container Native Virtualization (CNV) | Reporter: | Ruth Netser <rnetser> |
| Component: | Networking | Assignee: | Petr Horáček <phoracek> |
| Status: | CLOSED ERRATA | QA Contact: | Yossi Segev <ysegev> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.11.0 | CC: | cnv-qe-bugs, danken, ferferna, fge, jiji, jishi, klatouch, mshi, nashok, network-qe, phoracek, till, toneata, ysegev |
| Target Milestone: | --- | Keywords: | TestOnly |
| Target Release: | 4.11.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 2026621 | Environment: | |
| Last Closed: | 2022-09-14 19:30:30 UTC | Type: | --- |
| 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: | 2026621 | ||
| Bug Blocks: | 2040316, 2040317 | ||
|
Description
Ruth Netser
2022-04-13 19:36:48 UTC
Verified on a bare-metal cluster with
OCP 4.11 (4.11.0-0.nightly-2022-05-11-054135)
CNV 4.11.0
NetworkManager 1.32.10-5.el8_5
nmstate 1.2.1-1.el8.x86_64
1. On one of the cluster worker nodes - I searched for an Intel X710 device:
sh-4.4# lspci | grep 710
3b:00.0 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 02)
3b:00.1 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 02)
sh-4.4#
sh-4.4# ethtool -i ens2f0
driver: i40e
...
bus-info: 0000:3b:00.0
...
(once I found an X710 device, i searched for the interface that has that PCI address - 3b:00.0 in my case).
2. I applied the following policy:
ApiVersion: nmstate.io/v1
kind: NodeNetworkConfigurationPolicy
metadata:
name: br1test-nncp
spec:
desiredState:
interfaces:
- bridge:
options:
stp:
enabled: false
port:
- name: ens2f0
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
nodeSelector:
kubernetes.io/hostname: cnvqe-10.lab.eng.tlv2.redhat.com
3. After applying, I waited for the policy to complete configuration successfully.
[cnv-qe-jenkins@cnvqe-01 yossi]$ oc apply -f vlan-nncp.yaml
oc get nncp -wnodenetworkconfigurationpolicy.nmstate.io/br1test-nncp created
[cnv-qe-jenkins@cnvqe-01 yossi]$ oc get nncp -w
NAME STATUS REASON
br1test-nncp Progressing ConfigurationProgressing
br1test-nncp Progressing ConfigurationProgressing
br1test-nncp Progressing ConfigurationProgressing
br1test-nncp Available SuccessfullyConfigured
4. On the node on which I applied the policy (using nodeSelector), I verified that the bridge was created successfully.
[cnv-qe-jenkins@cnvqe-01 yossi]$ oc debug node/cnvqe-10.lab.eng.tlv2.redhat.com
Starting pod/cnvqe-10labengtlv2redhatcom-debug ...
To use host binaries, run `chroot /host`
Pod IP: 10.46.41.13
If you don't see a command prompt, try pressing enter.
sh-4.4# chroot /host
sh-4.4#
sh-4.4# nmcli c show
NAME UUID TYPE DEVICE
Wired Connection 47ca2063-95a4-4946-816e-6dfce656b73e ethernet eno1
...
br1test 0ea60ba8-e48a-4ad2-8078-0822f1e58126 bridge br1test
ens2f0 5447ef1c-f832-476e-9d52-19b3e1619dcb ethernet ens2f0
...
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 (Important: OpenShift Virtualization 4.11.0 Images security and bug fix 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/RHSA-2022:6526 |