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.
Verified with versions:
nmstate-1.0.2-14.el8_4.noarch
nispor-1.0.1-4.el8.x86_64
NetworkManager-1.30.0-10.el8_4.x86_64
Desired state applied:
---
routes:
config:
- destination: 0.0.0.0/0
next-hop-address: 0.0.0.0
next-hop-interface: dummy
table-id: 0
interfaces:
- name: dummy
type: dummy
state: up
ipv4:
enabled: true
address:
- ip: 192.0.2.1
prefix-length: 24
ipv6:
enabled: false
[06:19:34@ci-vm-10-0-137-181 ~]0# ip route
default via 10.0.139.254 dev eth0 proto dhcp metric 100
default dev dummy proto static scope link metric 550
10.0.136.0/22 dev eth0 proto kernel scope link src 10.0.137.181 metric 100
169.254.169.254 via 10.0.136.13 dev eth0 proto dhcp metric 100
192.0.2.0/24 dev dummy proto kernel scope link src 192.0.2.1 metric 550
#comment13 is the verification for 8.4.0.z, please ignore it.
Verified with versions:
nmstate-1.1.0-3.el8.noarch
nispor-1.1.1-1.el8.x86_64
NetworkManager-1.32.4-1.el8.x86_64
Desired state applied:
---
routes:
config:
- destination: 0.0.0.0/0
next-hop-address: 0.0.0.0
next-hop-interface: dummy
table-id: 0
interfaces:
- name: dummy
type: dummy
state: up
ipv4:
enabled: true
address:
- ip: 192.0.2.1
prefix-length: 24
ipv6:
enabled: false
[18:27:06@ibm-x3650m4-01-vm-12 ~]0# ip route
default via 10.16.215.254 dev ens3 proto dhcp metric 100
default dev dummy proto static scope link metric 550
10.16.214.0/23 dev ens3 proto kernel scope link src 10.16.214.14 metric 100
192.0.2.0/24 dev dummy proto kernel scope link src 192.0.2.1 metric 550
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 (nmstate 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/RHBA-2021:4157
Created attachment 1805767 [details] Reproducer Description of problem: nmstate fails verification phase for routes that have next-hop-address 0.0.0.0 Version-Release number of selected component (if applicable): nmstate-1.0.2-13 How reproducible: 100% Steps to Reproduce: 1. Run the reproducer Actual results: libnmstate.error.NmstateVerificationError: desired ======= --- routes: config: - destination: 0.0.0.0/0 next-hop-address: 0.0.0.0 next-hop-interface: dummy table-id: 254 current ======= --- routes: config: - destination: '' metric: 550 next-hop-address: '' next-hop-interface: dummy table-id: 254 difference ========== --- desired +++ current @@ -1,7 +1,8 @@ --- routes: config: - - destination: 0.0.0.0/0 - next-hop-address: 0.0.0.0 + - destination: '' + metric: 550 + next-hop-address: '' next-hop-interface: dummy table-id: 254 Expected results: Should pass