topotests: bgp_peer_type_multipath, fix duplicate nexthop removed check

An issue appears when BGP wants to add the 203.0.113.0/30 prefix from eBGP multiple paths: the 10.0.3.2 nexthop has not the 'fib' flag set, whereas it is expected. The test fails only when BGP nexthop group mode is used. The flag value does not change the behaviour. Only the nexthop which has not the 'duplicate nexthop removed' flag is not installed. Because the test deals with detecting the duplicated nexthop detection, do a check on the 'duplicate' flag. Signed-off-by: Philippe Guibert <[email protected]>
FRRouting · Mar 6, 2024 · 952ce66 · 952ce66
1 parent 30477d7
commit 952ce66
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 0 deletions.
diff --git a/tests/topotests/bgp_peer_type_multipath_relax/r1/prefix1-eBGP-confed.json b/tests/topotests/bgp_peer_type_multipath_relax/r1/prefix1-eBGP-confed.json
@@ -24,6 +24,7 @@
         },
         {
           "fib":true,
+          "duplicate":true,
           "ip":"10.0.3.2",
           "active":true
         }

diff --git a/tests/topotests/bgp_peer_type_multipath_relax/r1/prefix1-eBGP-iBGP.json b/tests/topotests/bgp_peer_type_multipath_relax/r1/prefix1-eBGP-iBGP.json
@@ -24,6 +24,7 @@
         },
         {
           "fib":true,
+          "duplicate":true,
           "ip":"10.0.3.2",
           "active":true
         }