What were you trying to do that didn't work?

Given a YAML file unformatted.yaml:

route-rules:
  config:
    - ip-from: 192.0.2.1/24
      priority: 1001
      route-table: 50
    - ip-to: 100::1/64
      priority: 1000
      route-table: 50

to create, nmstate converts the ip subnet to 192.0.2.0/24 and 100::/64 according to the subnet mask

But when wanting to delete them, simply append `state: absent` to the rule items, say unformatted-absent.yaml:

route-rules:
  config:
    - ip-from: 192.0.2.1/24
      priority: 1001
      route-table: 50
      state: absent
    - ip-to: 100::1/64
      priority: 1000
      route-table: 50
      state: absent

then apply it. In this case, nmstate literally uses 192.0.2.1/24 and 100::1/64, matches nothing to delete.

What is the impact of this issue to you?

I cannot remove the route rules by simply modifying creating file, I have to look up the current state or convert the subnet by myself then remove them.

Please provide the package NVR for which the bug is seen:

nmstate-2.2.38-1.el9.x86_64
NetworkManager-1.51.2-2.el9.x86_64

How reproducible is this bug?:

100%

Steps to reproduce

nmstatectl apply unformatted.yaml
ip rule
ip -6 rule
nmstatectl apply unformatted-absent.yaml
# still there
ip rule
ip -6 rule

Expected results

The rules are removed

The behavior (convert ip subnet or not) should be the same in route rules creation and deletion. 

Actual results