From 5575935eeefc2b316d681ad995e84b4b07862028 Mon Sep 17 00:00:00 2001 From: Stepan Blyshchak <38952541+stepanblyschak@users.noreply.github.com> Date: Thu, 31 Mar 2022 15:44:32 +0300 Subject: [PATCH] [neighsyncd] increase neighsyncd timeout (#2209) - What I did Increased the neighsyncd timeout. - Why I did it Restore_neigh takes a bit more time to start thus it could be that the neighsyncd timeout is not enough to wait for restore_neighbors - How I verified it py.test platform_tests/test_advanced_reboot.py::test_warm_reboot_sad[sad_lag_member] --inventory="../ansible/inventory,../ansible/veos" --host-pattern arc-switch1004 --module-path ../ansible/library/ --testbed arc-switch1004-t0-56 --testbed_file ../ansible/testbed.csv --allow_recover --log-cli-level info --skip_sanity Signed-off-by: Stepan Blyschak --- neighsyncd/neighsync.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/neighsyncd/neighsync.h b/neighsyncd/neighsync.h index 49a17ee6b663..b91392c4c021 100644 --- a/neighsyncd/neighsync.h +++ b/neighsyncd/neighsync.h @@ -14,7 +14,7 @@ * service to finish, should be longer than the restore_neighbors timeout value (110) * This should not happen, if happens, system is in a unknown state, we should exit. */ -#define RESTORE_NEIGH_WAIT_TIME_OUT 120 +#define RESTORE_NEIGH_WAIT_TIME_OUT 180 namespace swss {