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 1894139 - [RFE] Support VETH interface type
Summary: [RFE] Support VETH interface type
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: nmstate
Version: 8.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 8.4
Assignee: Fernando F. Mancera
QA Contact: Mingyu Shi
URL:
Whiteboard:
Depends On:
Blocks: 1885605
TreeView+ depends on / blocked
 
Reported: 2020-11-03 16:05 UTC by Edward Haas
Modified: 2021-05-18 15:18 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-18 15:17:45 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Edward Haas 2020-11-03 16:05:21 UTC 
Description of problem:
Nmstate can now be optionally deployed through kubernetes-nmstate [1] on kubernetes/OCP nodes to manage the node network configuration.

With the introduction of OVN on nodes, especially when the OVS bridge is connected to the node main interface, there is a need to bridge/connect between it and the Linux bridge based solutions some deployments depend on (e.g. kubevirt ). See [2] for an issue regarding this.

It is therefore requested to allow nmstate to manage veth interfaces which can be connected on one side to the OVS bridge and on the other side to the Linux bridge.

[OVS bridge]---veth---[Linux bridge]

Note: The link may be used as a trunk, but such details relate to the bridge ports rather than the veth itself.

Additional info:

Requested for the kubevirt/openshift-virtualization use case.

1. https://github.com/nmstate/kubernetes-nmstate
2. https://bugzilla.redhat.com/1885605
Comment 1 Fernando F. Mancera 2020-11-03 16:10:36 UTC 
Hello Edward,

I am working on it. Just to make it clear this bug will be considere as done or completed when nmstate would be capable of reporting and configuring Veth interfaces and its properties like "peer". Thank you!
Comment 2 Till Maas 2020-11-10 09:38:00 UTC 
(In reply to Fernando F. Mancera from comment #1)
> Hello Edward,
> 
> I am working on it. Just to make it clear this bug will be considere as done
> or completed when nmstate would be capable of reporting and configuring Veth
> interfaces and its properties like "peer". Thank you!

Another requirement that was requested via e-mail that should also be tested is this user story: "I can connect a Linux Bridge with an OVS Bridge using a veth pair".
Comment 3 Till Maas 2020-11-10 17:01:33 UTC 
This bug needs to be better scoped and investigated since NetworkManager is lacking support for veth interfaces.
Comment 7 Dan Kenigsberg 2021-01-22 10:33:44 UTC 
Would you link back to the patch fixing this, and possibly to the doc for this new feature?

I'd like to understand how to use it.
Comment 8 Fernando F. Mancera 2021-01-22 11:31:01 UTC 
(In reply to Dan Kenigsberg from comment #7)
> Would you link back to the patch fixing this, and possibly to the doc for
> this new feature?
> 
> I'd like to understand how to use it.

This is the link for the PR that was adding veth support. https://github.com/nmstate/nmstate/pull/1434

For the documentation, I am finishing the upstream documentation that will be available at nmstate.io. I will ping you when ready. Thanks!
Comment 9 Dan Kenigsberg 2021-01-22 12:29:16 UTC 
Thanks. I'd appreciate an example of connecting one of the peers to a Linux bridge, and the other to an ovs brige.
Comment 12 Mingyu Shi 2021-01-26 11:31:06 UTC 
Verified with versions:
nmstate-1.0.1-1.el8.noarch
nispor-1.0.1-2.el8.x86_64
NetworkManager-1.30.0-0.7.el8.x86_64

There are certain details need to discuss:
 * changing type between veth and ethernet
 * when a peer is in a netns
Comment 13 Fernando F. Mancera 2021-01-26 15:58:56 UTC 
(In reply to Dan Kenigsberg from comment #9)
> Thanks. I'd appreciate an example of connecting one of the peers to a Linux
> bridge, and the other to an ovs brige.

Please, find the upstream veth documentation in https://www.nmstate.io/features/veth.html

Thank you!
Comment 16 errata-xmlrpc 2021-05-18 15:17:45 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 (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-2021:1748
Note You need to log in before you can comment on or make changes to this bug.