Consider a topology with multiple logical routers, e.g.:

ovn-nbctl lr-add lr1
ovn-nbctl lrp-add lr1 lrp1 00:00:00:00:00:01 1.1.1.1/24

ovn-nbctl lr-add lr2
ovn-nbctl lrp-add lr2 lrp2 00:00:00:00:00:02 2.2.2.2/24

If the user needs to configure a route to the same prefix on both routers but makes a mistake when specifying the next hop IP the logs ovn-northd generates are ambiguous and not that helpful:

ovn-nbctl lr-route-add lr1 42.42.42.42/32 1.1.1.1
ovn-nbctl lr-route-add lr2 42.42.42.42/32 1.1.1.1

The second route is incorrect because lr2 doesn't have an IP in any subnet that includes 1.1.1.1.  In this case ovn-northd.log contains:

2024-09-09T15:23:57.149Z|00014|northd|WARN|No path for static route 42.42.42.42; next hop 1.1.1.1

The log is incomplete because it's not clear to the user if the problem is on lr1 or lr2.

A similar thing happens when (mis)configuring routing policies:

ovn-nbctl lr-policy-add lr1 1 "ip" reroute 1.1.1.1
ovn-nbctl lr-policy-add lr2 1 "ip" reroute 1.1.1.1

The log is:

2024-09-09T15:25:35.719Z|00017|northd|WARN|No path for routing policy priority 1; next hop 1.1.1.1

Ideally the two logs should be changed to include the router name.  That simplifies troubleshooting on the user side.