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.

Bug 2135595

Summary:	nmcli add type veth persistency issue
Product:	Red Hat Enterprise Linux 8	Reporter:	kevin <welin>
Component:	NetworkManager	Assignee:	NetworkManager Development Team <nm-team>
Status:	CLOSED DUPLICATE	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.6	CC:	bgalvani, lrintel, rkhan, sfaye, sukulkar, till
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	---
Hardware:	x86_64
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-01-24 09:21:43 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 kevin 2022-10-18 04:49:10 UTC

Description of problem:

hello, I have foudn nmcli add type veth persistency issue issue on RHEL 8.6, have any solution for this issue?

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

# hostnamectl
   Static hostname: ip-192-168-4-10.us-east-2.compute.internal
         Icon name: computer-vm
           Chassis: vm
        Machine ID: a63bb499444c40348efbe29996231d04
           Boot ID: 70a8d643fe814b8da1f80ffa2ddc7d51
    Virtualization: xen
  Operating System: Red Hat Enterprise Linux 8.6 (Ootpa)
       CPE OS Name: cpe:/o:redhat:enterprise_linux:8::baseos
            Kernel: Linux 4.18.0-372.9.1.el8.x86_64
      Architecture: x86-64

# NetworkManager -V
1.36.0-7.el8_6

How reproducible:

Steps to Reproduce:

# nmcli  connection add type veth con-name test11+ ifname test11 veth.peer test12 ip4 10.42.0.2
# nmcli  connection add type veth con-name test12+ ifname test12 veth.peer test11 ip4 10.42.0.1
# nmcli con up test11+
# nmcli con up test12+

# nmcli con show
NAME         UUID                                  TYPE      DEVICE
System eth0  5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03  ethernet  eth0
test11+      442ab16a-ee78-4bff-b008-b95b9b260704  veth      test11
test12+      e066f496-61c0-451d-8f91-5fef3384aa58  veth      test12

# nmcli dev
DEVICE      TYPE         STATE                   CONNECTION
eth0        ethernet     connected               System eth0
test11      ethernet     connected               test11+
test12      ethernet     connected               test12+

# ip link show type veth
13: test12@test11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 52:72:47:d3:91:b1 brd ff:ff:ff:ff:ff:ff
14: test11@test12: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 2e:2d:7d:e2:38:87 brd ff:ff:ff:ff:ff:ff


# reboot

Actual results:

# nmcli con show
NAME         UUID                                  TYPE      DEVICE
System eth0  5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03  ethernet  eth0
test12+      e066f496-61c0-451d-8f91-5fef3384aa58  veth      test12
test11+      442ab16a-ee78-4bff-b008-b95b9b260704  veth      --

# nmcli dev
DEVICE      TYPE         STATE                   CONNECTION
eth0        ethernet     connected               System eth0
test12      ethernet     connected               test12+

# ip link show type veth
3: test11@test12: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 0e:30:e4:a9:e9:ff brd ff:ff:ff:ff:ff:ff
4: test12@test11: <NO-CARRIER,BROADCAST,MULTICAST,UP,M-DOWN> mtu 1500 qdisc noqueue state LOWERLAYERDOWN mode DEFAULT group default qlen 1000
    link/ether b6:82:a9:00:18:6d brd ff:ff:ff:ff:ff:ff

So this result you can see that when after reboot, the veth test11+ has been lost, does it a BUG?

Expected results:

test11+ veth can automatically start after reboot

Additional info:

other person have raised a similar bug, I have found this bug have not solved so I open this new bug for continue to dive:

https://bugzilla.redhat.com/show_bug.cgi?id=1915284

Comment 1 sfaye 2023-01-24 09:21:43 UTC

This issue has been fixed in https://bugzilla.redhat.com/show_bug.cgi?id=2105956 (See comment https://bugzilla.redhat.com/show_bug.cgi?id=1915284#c10). Therefore, I am closing this as duplicate. Please feel free to reopen if needed.

*** This bug has been marked as a duplicate of bug 2105956 ***