-
Bug
-
Resolution: Done-Errata
-
Normal
-
rhel-9.2.0
-
NetworkManager-1.45.9-1.el9
-
None
-
Moderate
-
2
-
rhel-sst-network-management
-
ssg_networking
-
22
-
1
-
Customer/Partner Jira ID Case ID Status Details OpenShift RHEL-1682No customer case When creating an ECMP route with nmstate on NetworkManager, an extra static non-ECMP route appears alongside the intended ECMP route. This is due to NetworkManager not removing the pre-existing single hop route when merging to the desired ECMP route. A fix is proposed to ensure leftover routes are removed when merging to a new ECMP with multiple next hops. The customer has a workaround and the issue is being fixed and is waiting for QA verification Customer/Partner Jira ID Case ID Status Details OpenShift RHEL-1682 No customer case When creating an ECMP route with nmstate on NetworkManager, an extra static non-ECMP route appears alongside the intended ECMP route. This is due to NetworkManager not removing the pre-existing single hop route when merging to the desired ECMP route. A fix is proposed to ensure leftover routes are removed when merging to a new ECMP with multiple next hops. The customer has a workaround and the issue is being fixed and is waiting for QA verification -
QE ack, Dev ack
-
False
-
-
None
-
NMT - RHEL 8.10/9.4 DTM 00, NMT - RHEL 8.10/9.4 DTM 14
-
Pass
-
None
-
If docs needed, set a value
-
-
x86_64
-
None
Description of problem:
When creating ECMP route via nmstate, we noticed extra static non-ECMP route been created beside the ECMP one:
198.51.100.0/24 via 192.0.2.1 dev dummy1 proto static metric 150
198.51.100.0/24 proto static metric 150
nexthop via 192.0.2.1 dev dummy1 weight 2
nexthop via 192.0.2.2 dev dummy2 weight 25
Version-Release number of selected component (if applicable):
NetworkManager-1.45.1-32541.copr.194b381d38.el9.x86_64
How reproducible:
100%
Steps to Reproduce:
1.
echo '
---
interfaces:
- name: dummy1
type: dummy
state: up
ipv4:
address:
- ip: 192.0.2.251
prefix-length: 24
dhcp: false
enabled: true
- name: dummy2
type: dummy
state: up
ipv4:
address:
- ip: 192.0.2.252
prefix-length: 24
dhcp: false
enabled: true
routes:
config:
- destination: 198.51.100.0/24
metric: 150
next-hop-address: 192.0.2.1
next-hop-interface: dummy1
weight: 2
table-id: 254
- destination: 198.51.100.0/24
metric: 150
next-hop-address: 192.0.2.2
next-hop-interface: dummy2
weight: 25
table-id: 254' | sudo nmstatectl set -
2. ip route show
3.
Actual results:
198.51.100.0/24 via 192.0.2.1 dev dummy1 proto static metric 150
198.51.100.0/24 proto static metric 150
nexthop via 192.0.2.1 dev dummy1 weight 2
nexthop via 192.0.2.2 dev dummy2 weight 25
Expected results:
198.51.100.0/24 proto static metric 150
nexthop via 192.0.2.1 dev dummy1 weight 2
nexthop via 192.0.2.2 dev dummy2 weight 25
Additional info:
`sudo nmcli c up dummy1` will clear the extra non-ECMP route.
- external trackers
- links to
-
RHBA-2023:120156
NetworkManager bug fix and enhancement update
- mentioned on
