Bug 2166630
| Summary: | Allow to change the priority of the local routing table | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Federico Paolinelli <fpaoline> | |
| Component: | nmstate | Assignee: | Fernando F. Mancera <ferferna> | |
| Status: | CLOSED WONTFIX | QA Contact: | Mingyu Shi <mshi> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 9.0 | CC: | fbaudin, ferferna, fge, jiji, jishi, mshi, network-qe, sfaye, till | |
| Target Milestone: | rc | Keywords: | Triaged | |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
|
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | No Doc Update | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 2167805 (view as bug list) | Environment: | ||
| Last Closed: | 2023-06-26 09:07:43 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 2167805 | |||
The use case is describe at https://www.dasblinkenlichten.com/working-with-linux-vrfs/ *** Bug 2171374 has been marked as a duplicate of this bug. *** According to Federico Paolinelli, this RFE is medium priority now. Since OpenShift 5G Telco team found new approach on solving their use case, this feature is not required any more. Modifying the local route table is dangerous(break all network communication), this is no valid use case anymore even for upstream users. Closing as won't fix. Feel free to reopen if you need this feature again. |
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: