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 there is no suitbale interface to store route rules, nmstate will store them in loopback profile, but they cannot be deleted with nmstate.

Version-Release number of selected component (if applicable):
nmstate-2.2.7-1.el9.x86_64
nispor-1.2.9-1.el9.x86_64
NetworkManager-1.41.90-1.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
echo 'route-rules:
  config:
    - ip-from: 192.0.2.0/24
      route-table: 200
    - action: blackhole
      ip-from: 172.19.40.0/24
      route-table: 200
    - ip-from: 10.0.2.0/24
      route-table: 200
' | nmstatectl set

echo 'route-rules:
  config:
    - ip-from: 192.0.2.0/24
      route-table: 200
      state: absent
    - action: blackhole
      ip-from: 172.19.40.0/24
      route-table: 200
      state: absent
    - ip-from: 10.0.2.0/24
      route-table: 200
      state: absent' | nmstatectl set

Actual results:
NmstateError: VerificationError: Desired absent route rule state: absent family: ipv4 ip-from: 192.0.2.0/24 priority: 30000 route-table: 200 still found after apply: family: ipv4 ip-from: 192.0.2.0/24 priority: 30000 route-table: 200

Expected results:
The rules were removed

Additional info:

The local route table support will be fixed in bug 2166630

Current, customer cannot hit this problem, because 9.2 code is not shipped to any customer

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