Bug 1785130

Currently, route or routeset require related interface been included in desired state.

As I mentioned in bug 1748389, it's a massive change. Moving to RHEL 8.3.

Upstream tracker: https://github.com/nmstate/nmstate/issues/942

Verified with versions:
nmstate-0.3.2-1.el8.noarch
NetworkManager-1.26.0-0.1.el8.x86_64
DISTRO=RHEL-8.3.0-20200629.n.0
Linux hp-dl380pg8-09.rhts.eng.pek2.redhat.com 4.18.0-221.el8.x86_64 #1 SMP Thu Jun 25 20:58:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Run as the below successfully:
ip link add eth1 type veth peer name eth1.ep
ip link add eth2 type veth peer name eth2.ep
ip link set eth1 up
ip link set eth1.ep up
ip link set eth2 up
ip link set eth2.ep up
nmcli device set eth1 managed yes
nmcli device set eth2 managed yes

cat > route_rules.yaml << EOF
---
interfaces:
  - name: eth1
    type: ethernet
    state: up
    ipv4:
      address:
      - ip: 192.0.2.251
        prefix-length: 24
      dhcp: false
      enabled: true
  - name: eth2
    type: ethernet
    state: up
    ipv4:
      address:
      - ip: 198.51.100.251
        prefix-length: 24
      dhcp: false
      enabled: true
route-rules:
  config:
  - ip-to: 192.0.2.0/24
    priority: 1000
    route-table: 50
  - ip-from: 192.0.2.0/24
    priority: 1000
    route-table: 50
  - ip-to: 198.51.100.0/24
    priority: 1000
    route-table: 51
  - ip-from: 198.51.100.0/24
    priority: 1000
    route-table: 51
routes:
  config:
  - destination: 0.0.0.0/0
    metric: 150
    next-hop-address: 192.0.2.1
    next-hop-interface: eth1
    table-id: 50
  - destination: 0.0.0.0/0
    metric: 150
    next-hop-address: 198.51.100.1
    next-hop-interface: eth2
    table-id: 51
EOF

nmstatectl set route_rules.yaml

cat > dummy1.yaml << EOF
---
interfaces:
  - name: dummy1
    type: dummy
    state: up
EOF

nmstatectl set dummy1.yaml 
2020-06-30 14:55:47,880 root         DEBUG    Async action: Create checkpoint started
2020-06-30 14:55:47,887 root         DEBUG    Checkpoint None created for all devices
2020-06-30 14:55:47,887 root         DEBUG    Async action: Create checkpoint finished
2020-06-30 14:55:47,890 root         DEBUG    Async action: Add profile: dummy1 started
2020-06-30 14:55:47,900 root         DEBUG    Async action: Add profile: dummy1 finished
2020-06-30 14:55:47,901 root         DEBUG    Async action: Activate profile: dummy1 started
2020-06-30 14:55:47,929 root         DEBUG    Connection activation initiated: dev=dummy1, con-state=<enum NM_ACTIVE_CONNECTION_STATE_ACTIVATING of type NM.ActiveConnectionState>
2020-06-30 14:55:47,964 root         DEBUG    Connection activation succeeded: dev=dummy1, con-state=<enum NM_ACTIVE_CONNECTION_STATE_ACTIVATED of type NM.ActiveConnectionState>, dev-state=<enum NM_DEVICE_STATE_ACTIVATED of type NM.DeviceState>, state-flags=<flags NM_ACTIVATION_STATE_FLAG_LAYER2_READY | NM_ACTIVATION_STATE_FLAG_IP4_READY | NM_ACTIVATION_STATE_FLAG_IP6_READY of type NM.ActivationStateFlags>
2020-06-30 14:55:47,965 root         DEBUG    Async action: Activate profile: dummy1 finished
2020-06-30 14:55:48,506 root         DEBUG    Checkpoint /org/freedesktop/NetworkManager/Checkpoint/31 destroyed
2020-06-30 14:55:48,506 root         DEBUG    Async action: Destroy checkpoint /org/freedesktop/NetworkManager/Checkpoint/31 started
2020-06-30 14:55:48,511 root         DEBUG    Checkpoint /org/freedesktop/NetworkManager/Checkpoint/31 destroy executed
2020-06-30 14:55:48,511 root         DEBUG    Async action: Destroy checkpoint /org/freedesktop/NetworkManager/Checkpoint/31 finished
Desired state applied: 
---
interfaces:
- name: dummy1
  type: dummy
  state: up

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-2020:4696