From: Chris Horn Date: Thu, 29 Apr 2021 18:09:07 +0000 (-0500) Subject: LU-14654 tests: Ensure recovery_limit zero works as expected X-Git-Tag: 2.14.53~66 X-Git-Url: https://git.whamcloud.com/?p=fs%2Flustre-release.git;a=commitdiff_plain;h=8d1895f2f69bd2eec3ff6af5eb356740fa2c8766 LU-14654 tests: Ensure recovery_limit zero works as expected When lnet_recovery_limit is set to zero (the default) peer NIs are eligible for recovery pings indefinitely. Verify this functionality by modifying sanity-lnet test_211 to use recovery_limit 0 to make a peer NI re-eligible for recovery. Test-Parameters: trivial testlist=sanity-lnet HPE-bug-id: LUS-9953 Signed-off-by: Chris Horn Change-Id: I00cb0940133e15ec73491e875d08b6db2bff3fe5 Reviewed-on: https://review.whamcloud.com/43502 Tested-by: jenkins Tested-by: Maloo Reviewed-by: Alexander Boyko Reviewed-by: Cyril Bordage Reviewed-by: Oleg Drokin --- diff --git a/lustre/tests/sanity-lnet.sh b/lustre/tests/sanity-lnet.sh index 8d232ff..7b1bd61 100755 --- a/lustre/tests/sanity-lnet.sh +++ b/lustre/tests/sanity-lnet.sh @@ -1844,13 +1844,16 @@ test_211() { # Set health to force it back onto the recovery queue. Set to 500 means # in 5 seconds it should be back at maximum value. We'll wait a couple # more seconds than that to be safe. - # NB: we need to increase the recovery limit so the peer NI is + # NB: we reset the recovery limit to 0 (indefinite) so the peer NI is # eligible again - do_lnetctl set recovery_limit 50 || + do_lnetctl set recovery_limit 0 || error "failed to set recovery_limit" $LNETCTL peer set --nid $prim_nid --health 500 + check_nid_in_recovq "-p" 1 + check_ping_count "peer_ni" "2" + sleep 7 check_nid_in_recovq "-p" 0