lnet_health_post() can race with recovery pings, so we should
wait to delete the drop rules until after we've gathered the
health and resend values.
Lustre-change: https://review.whamcloud.com/47998
Lustre-commit:
8caec97d5e89eefe250edb64e6f7ad61e12a9d71
Test-Parameters: trivial testlist=sanity-lnet
Fixes:
79ab053562 ("LU-13569 lnet: Deprecate lnet_recovery_interval")
Signed-off-by: Chris Horn <chris.horn@hpe.com>
Change-Id: Ia7595e015809f796cafcc40382d98ab66a708a49
Reviewed-on: https://review.whamcloud.com/c/ex/lustre-release/+/54439
Tested-by: jenkins <devops@whamcloud.com>
Tested-by: Maloo <maloo@whamcloud.com>
Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
restore_lnet_params
+ $LCTL net_drop_del -a
+
do_lnetctl peer set --health 1000 --all
do_lnetctl net set --health 1000 --all
do_lnetctl discover ${RNIDS[0]} &&
error "Should have failed"
- $LCTL net_drop_del -a
lnet_health_post
do_lnetctl discover ${RNIDS[0]} &&
error "Should have failed"
- $LCTL net_drop_del -a
lnet_health_post