This issue is seen on the latest master with FRR.
root@str-s6100-acs-5:/home/admin# ip route add 2.2.2.0/24 nexthop via 10.0.0.55
root@str-s6100-acs-5:/home/admin# ip route list match 2.2.2.2
default proto 186 src 10.1.0.32 metric 20
nexthop via 10.0.0.13 dev PortChannel0011 weight 1
nexthop via 10.0.0.1 dev PortChannel0002 weight 1
nexthop via 10.0.0.5 dev PortChannel0005 weight 1
nexthop via 10.0.0.9 dev PortChannel0008 weight 1
2.2.2.0/24 via 10.0.0.55 dev PortChannel0016
127.0.0.1:6379> hgetall "ROUTE_TABLE:2.2.2.0/24"
1) "nexthop"
2) "10.0.0.55"
3) "ifname"
4) "PortChannel0016"
root@str-s6100-acs-5:/home/admin# ip route change 2.2.2.0/24 nexthop via 10.0.0.55 nexthop via 10.0.0.57
root@str-s6100-acs-5:/home/admin# ip route list match 2.2.2.2
default proto 186 src 10.1.0.32 metric 20
nexthop via 10.0.0.13 dev PortChannel0011 weight 1
nexthop via 10.0.0.1 dev PortChannel0002 weight 1
nexthop via 10.0.0.5 dev PortChannel0005 weight 1
nexthop via 10.0.0.9 dev PortChannel0008 weight 1
2.2.2.0/24
nexthop via 10.0.0.55 dev PortChannel0016 weight 1
nexthop via 10.0.0.57 dev PortChannel0017 weight 1
127.0.0.1:6379> hgetall "ROUTE_TABLE:2.2.2.0/24"
(empty list or set)
root@str-s6100-acs-5:/home/admin# ip route change 2.2.2.0/24 nexthop via 10.0.0.55 nexthop via 10.0.0.57 nexthop via 10.0.0.59
root@str-s6100-acs-5:/home/admin# ip route list match 2.2.2.2
default proto 186 src 10.1.0.32 metric 20
nexthop via 10.0.0.13 dev PortChannel0011 weight 1
nexthop via 10.0.0.1 dev PortChannel0002 weight 1
nexthop via 10.0.0.5 dev PortChannel0005 weight 1
nexthop via 10.0.0.9 dev PortChannel0008 weight 1
2.2.2.0/24
nexthop via 10.0.0.55 dev PortChannel0016 weight 1
nexthop via 10.0.0.57 dev PortChannel0017 weight 1
nexthop via 10.0.0.59 dev PortChannel0018 weight 1
127.0.0.1:6379> hgetall "ROUTE_TABLE:2.2.2.0/24"
1) "nexthop"
2) "10.0.0.55,10.0.0.57,10.0.0.59"
3) "ifname"
4) "PortChannel0016,PortChannel0017,PortChannel0018"
This issue is seen on the latest master with FRR.