+++ This bug was initially created as a clone of Bug #2166630 +++
Description of problem:
When using a vrf, a rule like
1000: from all lookup [l3mdev-table]
is created, so it's common practice to change the priority of the rule associated with the "local" table to a higher value.
The issue is that it's not currently possible with nmstate.
A desired state of
route-rules:
config:
- route-table: 255
priority: 0
family: ipv4
state: absent
- route-table: 255
priority: 32765
family: ipv4
Will result in an error.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Apply the configuration above
2.
3.
Actual results:
The configuration is refused
Expected results:
The priority of the rule related to the "local" route table changes.
Additional info:
--- Additional comment from Gris Ge on 2023-02-07 15:16:28 UTC ---
The use case is describe at https://www.dasblinkenlichten.com/working-with-linux-vrfs/
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 (NetworkManager 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-2023:2485