diff options
| author | Louis Scalbert <louis.scalbert@6wind.com> | 2024-10-24 15:35:35 +0200 |
|---|---|---|
| committer | Louis Scalbert <louis.scalbert@6wind.com> | 2024-10-25 14:17:20 +0200 |
| commit | 771284474d3660e5b7808b4f81038307bc63b585 (patch) | |
| tree | 0298ea3ec6f501ac721407b40d7fc828af9efb40 /tools/frr-llvm-debuginfo.cpp | |
| parent | tests: factorize code in bgp_bmp_vrf (diff) | |
| download | frr-771284474d3660e5b7808b4f81038307bc63b585.tar.xz frr-771284474d3660e5b7808b4f81038307bc63b585.zip | |
tests: fix bgp_bmp race condition
The bgp_bmp topotest is randomly failing with similar messages:
> 2024-10-24 16:59:03,037 ERROR: topo: test failed at "bgp_bmp.test_bgp_bmp/test_bmp_bgp_unicast": Checking the updated prefixes has failed ! Generated JSON diff error report:
>
> $->pre-policy->update: expected has key '172.31.0.15/32' which is not present in output
It is particularly unsuccessful when run with valgrind:
> python3 -m pytest -vvss --valgrind-leak-kinds=all --valgrind-extra --valgrind-memleaks bgp_bmp
bgp_bmp is configuring a BMP policy on r1 and then some static BGP
prefixes on r2. If for some reasons, the BGP UPDATE arrives to r1 before
the BMP configuration is operational, the UPDATE is not sent to the BMP
server and the test fails.
Pre-configure the BMP policies at startup to avoid this race condition.
Signed-off-by: Louis Scalbert <louis.scalbert@6wind.com>
Diffstat (limited to 'tools/frr-llvm-debuginfo.cpp')
0 files changed, 0 insertions, 0 deletions