-
Story
-
Resolution: Unresolved
-
Major
-
None
-
nmstate-2.2.56-1.el10
-
None
-
rhel-net-mgmt
-
3
-
False
-
False
-
-
Yes
-
None
-
-
Pass
-
None
-
Unspecified Release Note Type - Unknown
-
Unspecified
-
Unspecified
-
Unspecified
-
None
Goal
- As a user configuring routes associated with VRFs, I want a stable way to reference the VRF table id. Otherwise, on reboots the id can change and then manual updates are needed to reconcile the route definition.
Acceptance criteria
Support a route configuration such as the following:
routes:
config:
- destination: b.b.b.b/32
metric: 150
next-hop-address: c.c.c.c
next-hop-interface: bond0.301
vrf-name: dmz
For more details, see the linked RFE.
- is related to
-
OPNET-690 Add support for VRF name in routes
-
- Testing
-
-
RFE-7795 Make route table ID predictable for VRF lite CUDNs
-
- Approved
-
- links to
-
RHBA-2025:154283
nmstate update