Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2084363

Summary: [RFE] [CNV] Support setting vlan-protocol in bridge options
Product: OpenShift Container Platform Reporter: Germano Veit Michel <gveitmic>
Component: NetworkingAssignee: Ben Nemec <bnemec>
Networking sub component: kubernetes-nmstate QA Contact: Aleksandra Malykhin <amalykhi>
Status: CLOSED DEFERRED Docs Contact:
Severity: low    
Priority: unspecified CC: davegord
Version: 4.10   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2084478 (view as bug list) Environment:
Last Closed: 2023-01-04 20:46:20 UTC 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: 2084474, 2084478    
Bug Blocks:    

Description Germano Veit Michel 2022-05-12 00:20:28 UTC 
Description of problem:

To make use of 802.3ad S-tag and C-tags, the linux bridge requires the option vlan-protocol set to 802.1ad, so it can add S-tags of ethertype 0x88A8 and does the correct forwarding. If this is set to 802.1Q (default, 0x8100), the bridge will drop the guest tagged frames as it tries to deliver locally (not supported).

Currently, for this to work, the user needs to manually edit the bridge on each node:

# nmcli con mod br1 bridge.vlan-protocol 802.1ad
# nmcli con down br1
# nmcli con up br1

Its this setting that ends up changed with that.
# cat /sys/class/net/br1/bridge/vlan_protocol 

This is probably a kubernetes-nmstate RFE, and depending if you want to set that manually like was done with vlan-filtering via script a while ago (I think?), an nmstate RFE too. But I'll leave these decisions to you to open the child RFE if you need.
Comment 2 Petr Horáček 2022-05-26 09:46:47 UTC 
Setting the target to future as this is waiting for an RFE on nmstate
Comment 3 Petr Horáček 2022-07-21 08:24:10 UTC 
Support for vlan-protocol will be added to nmstate in 9.1, so circa in OpenShift 4.14.

Moving to the standalone operator to continue the tracking there.