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
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:3071
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