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

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.

Description of problem:

NetworkManager does not support VETH configuration. When a VETH interface is created using iproute2, NetworkManager consider it as ethernet interface and it is not possible to configure the peer name or to create a new veth interface.

Nmstate requires this feature in order to support VETH interfaces too.

Version-Release number of selected component (if applicable):

1.30

Actual results:

It is not possible to create a veth interface using nmcli or NetworkManager API.

Expected results:

Using nmcli or NetworkManager API it is possible to create a veth device with a veth setting containing the peer name. This way, NetworkManager is supporting persistent state and rollback on veth interfaces.

In addition, it should not break any existing feature or use case related to veth. Therefore, if an user creates a veth using iproute2, then NetworkManager will consider it as ethernet device unless the user applies a veth setting to it.

Additional info:

Upstream MR: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/682

we still have some issues to be solved
https://bugzilla.redhat.com/show_bug.cgi?id=1915284 
https://bugzilla.redhat.com/show_bug.cgi?id=1915278 
https://bugzilla.redhat.com/show_bug.cgi?id=1915276

but the functionality is in and working

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 (Moderate: NetworkManager and libnma security, 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/RHSA-2021:1574