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 2111959 - [RFE] Support VLAN trunk mode and and trunk-tags range for OVS-bridge
Summary: [RFE] Support VLAN trunk mode and and trunk-tags range for OVS-bridge
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: NetworkManager
Version: 9.2
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: 9.2
Assignee: Beniamino Galvani
QA Contact: Vladimir Benes
URL:
Whiteboard:
Depends On:
Blocks: 2111398
TreeView+ depends on / blocked
 
Reported: 2022-07-28 14:14 UTC by Ana Cabral
Modified: 2023-05-09 10:30 UTC (History)
15 users (show)

Fixed In Version: NetworkManager-1.41.6-1.el9
Doc Type: No Doc Update
Doc Text:
Clone Of: 2111398
Environment:
Last Closed: 2023-05-09 08:17:27 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker NMT-528 0 None None None 2023-05-09 10:30:09 UTC
Red Hat Issue Tracker RHELPLAN-129472 0 None None None 2022-07-28 14:38:53 UTC
Red Hat Product Errata RHBA-2023:2485 0 None None None 2023-05-09 08:17:51 UTC
freedesktop.org Gitlab NetworkManager NetworkManager-ci merge_requests 1263 0 None merged ovs: add ovs-trunks into vlans ovs test 1.41.6 version 2022-12-08 18:46:06 UTC
freedesktop.org Gitlab NetworkManager NetworkManager merge_requests 1467 0 None merged Support ovs-port trunks 2022-11-25 13:26:37 UTC

Comment 1 Beniamino Galvani 2022-11-21 10:19:54 UTC 
Acceptance criteria:

Given a system using NetworkManager to create ovs interfaces
When the "ovs-port.trunks" property of a profile is set to a list of VLANs (for example: 10, 20, 30, 40)
Then after activation such VLANs are configured as trunks of the port and are visible in "ovs-vsctl show":
    Port ovs-port
        trunks: [10, 20, 30, 40]

Given a system using NetworkManager to create ovs interfaces
When the "ovs-port.trunks" is set to one or more ranges of VLANs (for example: 10-15, 20, 30-32)
Then such VLANs are configured as trunks of the port and are visible in "ovs-vsctl show":
    Port ovs-port
	trunks: [10, 11, 12, 13, 14, 15, 20, 30, 31, 32]

Given a system using NetworkManager to create ovs interfaces
When the user tries to set an invalid range of VLAN trunks in a profile:
 * 4096       (out of [0,4095] interval)
 * 20-10      (range is invalid)
 * 10-20, 15  (overlap of ranges)
Then such value is rejected
Comment 6 errata-xmlrpc 2023-05-09 08:17:27 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 (NetworkManager 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-2023:2485
Note You need to log in before you can comment on or make changes to this bug.