Bug 2084474
Summary: | [RFE] [RHEL] Support configuring bridge.vlan-protocol | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Germano Veit Michel <gveitmic> |
Component: | nmstate | Assignee: | Gris Ge <fge> |
Status: | CLOSED ERRATA | QA Contact: | Mingyu Shi <mshi> |
Severity: | medium | Docs Contact: | Jaroslav Klech <jklech> |
Priority: | unspecified | ||
Version: | 9.1 | CC: | ellorent, ferferna, fge, germano, jiji, jishi, jklech, network-qe, phoracek, sfaye, till |
Target Milestone: | rc | Keywords: | FutureFeature, Triaged |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: |
.Support for the 802.ad `vlan-protocol` option in `nmstate`
The `nmstate` API now supports creating the `linux-bridge` interfaces using the 802.ad `vlan-protocol` option. This feature enables the configuration of Service-Tag VLANs. The following example illustrates usage of this functionality in a `yaml` configuration file.
----
---
interfaces:
- name: br0
type: linux-bridge
state: up
bridge:
options:
vlan-protocol: 802.1ad
port:
- name: eth1
vlan:
mode: trunk
trunk-tags:
- id: 500
----
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2022-11-15 10:00:45 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: | |||
Bug Blocks: | 2084363, 2084478 |
Description
Germano Veit Michel
2022-05-12 08:36:25 UTC
*** Bug 2084478 has been marked as a duplicate of this bug. *** Patch posted to https://github.com/nmstate/nmstate/pull/1938 Adding support of linux bridge VLAN protocol: 802.1q(default) and 802.1ad. Example yaml: ```yaml --- interfaces: - name: br0 type: linux-bridge state: up bridge: options: vlan-protocol: 802.1ad port: - name: eth1 vlan: mode: trunk trunk-tags: - id: 500 ``` I have tested this manually. Verified with: nmstate-2.1.3-1.el9.x86_64 NetworkManager-1.39.10-1.el9.x86_64 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 (nmstate 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/RHBA-2022:7991 |