Bug 1901523

Summary: RFE: Support configuring VETH interfaces
Product: Red Hat Enterprise Linux 8 Reporter: Fernando F. Mancera <ferferna>
Component: NetworkManagerAssignee: Fernando F. Mancera <ferferna>
Status: CLOSED ERRATA QA Contact: Vladimir Benes <vbenes>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.4CC: acardace, atragler, bgalvani, lrintel, phoracek, rkhan, sukulkar, till, vbenes
Target Milestone: rcKeywords: FutureFeature, Triaged
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: NetworkManager-1.30.0-0.5.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-18 13:32:37 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:

Description Fernando F. Mancera 2020-11-25 13:59:30 UTC 
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:
Comment 1 Fernando F. Mancera 2020-11-25 14:01:39 UTC 
Upstream MR: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/682
Comment 4 Vladimir Benes 2021-01-12 12:34:41 UTC 
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
Comment 8 errata-xmlrpc 2021-05-18 13:32:37 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 (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