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 2036023

Summary: veth peer got deactivated after rebooting
Product: Red Hat Enterprise Linux 8 Reporter: Mingyu Shi <mshi>
Component: nmstateAssignee: Gris Ge <fge>
Status: CLOSED DUPLICATE QA Contact: Mingyu Shi <mshi>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.6CC: ferferna, jiji, jishi, network-qe, sfaye, till
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-07-12 11:35:02 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 Mingyu Shi 2021-12-29 10:37:43 UTC
Description of problem:
Created a veth peer with nmstate, after rebooting, one peer got deactivated.

Version-Release number of selected component (if applicable):
nmstate-1.2.0-1.el8.x86_64
nispor-1.2.2-1.el8.x86_64
NetworkManager-1.36.0-0.3.el8.x86_64

How reproducible:
100%

Steps to Reproduce:
echo "
interfaces:
- name: veth0
  type: veth
  state: up
  veth:
    peer: veth0_ep
" | nmstatectl apply -
reboot

# after rebooting:
nmcli con show

Actual results:
veth0(or maybe veth0_ep) got deactivated:
NAME      UUID                                  TYPE      DEVICE   
eno1      78219838-da78-4437-bd5a-1de38c057043  ethernet  eno1     
veth0_ep  e54287c2-e77e-43d1-ae4a-9862c5dc12e8  veth      veth0_ep 
eno2      bfc36316-ed6f-407f-9e5f-8631a1d022a4  ethernet  --       
eno3      9cea608a-24cd-493a-83ee-a71d3da405bf  ethernet  --       
eno4      7387925e-c9fc-43ae-8d6c-8db253d5df4e  ethernet  --       
veth0     128fe2f1-14fe-4c9b-8a50-cd1c6b2c5acf  veth      --   

Expected results:
Both peers keep activated.

Additional info:

Comment 3 Gris Ge 2022-07-11 10:51:23 UTC
This issue is not fixed. move back to new state.

Comment 5 Gris Ge 2022-07-12 11:35:02 UTC
Closing as dup of bug 2105956 which also have openshift assisted installer use case attached.

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