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:
When taking a veth absent, if not present its peer in desired state, then peer's connection will remain. That causes NM recreate veth peer on timeout.

Version-Release number of selected component (if applicable):
nmstate-1.0.2-5.el8.noarch
nispor-1.0.1-4.el8.x86_64
NetworkManager-1.30.0-4.el8.x86_64

How reproducible:
100%

Steps to Reproduce:
echo "interfaces:
- name: veth0
  type: veth
  state: up
  veth:
    peer: veth0_ep" | nmstatectl set -
echo "interfaces:
- name: veth0
  type: veth
  state: absent" | nmstatectl set -
ip link show veth0
nmcli con

Actual results:
NM connection of veth0_ep remained
After a timeout, NM will activate it again, that causes veth0 and veth0_ep come back

Expected results:
Remove veth0 and veth0_ep from kernel and NM connections 

Additional info:

Changing to RHEL 9 and this is already fixed by rust.

For RHEL 8, no need to fix this anymore.