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 1845216 - Support interface name as OVS patch peer
Summary: Support interface name as OVS patch peer
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Beniamino Galvani
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-08 16:54 UTC by Beniamino Galvani
Modified: 2020-11-04 01:51 UTC (History)
9 users (show)

Fixed In Version: NetworkManager-1.26.0-0.1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-04 01:50:15 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:4499 0 None None None 2020-11-04 01:50:36 UTC

Description Beniamino Galvani 2020-06-08 16:54:40 UTC 
Description of problem:

Currently NM accepts only IP addresses as peers for an OVS patch. It should accept any interface name.

nmcli connection add type ovs-interface ifname patch1 \
    master port-patch1 \
    ovs-interface.type patch \
    ovs-patch.peer patch0
Comment 1 Beniamino Galvani 2020-06-09 11:35:04 UTC 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/534/commits
Comment 2 Beniamino Galvani 2020-06-10 15:59:03 UTC 
Fix merged upstream.
Comment 3 Beniamino Galvani 2020-06-10 16:11:32 UTC 
Reproducer:

# nmcli connection add type ovs-bridge ifname ovsbr0 con-name ovsbr0+
# nmcli connection add type ovs-port ifname port0 master ovsbr0 con-name ovsport0+
# nmcli connection add type ovs-interface ifname patch0 master port0 ovs-interface.type patch ovs-patch.peer patch1 con-name ovspatch0+

# nmcli connection add type ovs-bridge ifname ovsbr1 con-name ovsbr1+
# nmcli connection add type ovs-port ifname port1 master ovsbr1 con-name ovsport1+
# nmcli connection add type ovs-interface ifname patch1 master port1 ovs-interface.type patch ovs-patch.peer patch0 con-name ovspatch1+

# ovs-vsctl show
    Bridge "ovsbr1"
        Port "port1"
            Interface "patch1"
                type: patch
                options: {peer="patch0"}
    Bridge "ovsbr0"
        Port "port0"
            Interface "patch0"
                type: patch
                options: {peer="patch1"}
Comment 6 Vladimir Benes 2020-07-08 10:48:38 UTC 
CI test added:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager-ci/-/merge_requests/599
Comment 9 errata-xmlrpc 2020-11-04 01:50:15 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-2020:4499
Note You need to log in before you can comment on or make changes to this bug.