-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
4.14
-
Important
-
No
-
False
-
-
-
-
workaround is to rebuild OVN db on egressing node
-
-
-
Description of problem:
Under some circumstances (not clear exactly which ones), the OVN databases of 2 nodes ended up having 2 src-ip static routes in ovn_cluster_router instead of one: one of them points to the correct IP of the rtoj-GR_${NODE_NAME} LRP and one points to a wrong IP on the join subnet (that IP is not used in any other LRP or LSP).
Both static routes are taken into consideration while routing traffic out from the cluster, so packets that use the right route are able to egress while the packets that use the wrong route are dropped.
Version-Release number of selected component (if applicable):
Reproduced in 4.14.20
How reproducible:
At least once. Only 2 nodes of the cluster.
Steps to Reproduce:
(Not sure, it was just found after investigation of strange packet drop)
Actual results:
Wrong static route to some non-existent IP in the join subnet. Intermittent packet drop.
Expected results:
No wrong static routes. No packet drop.
Additional info:
This can be workarounded by wiping the OVN databases of the impacted node.