From b47cba9ddd7305281d2e4e7a7daae9c951e37f4a Mon Sep 17 00:00:00 2001 From: Jozef Behran Date: Tue, 12 Apr 2016 20:30:47 +0200 Subject: [PATCH] Fix spurious warnings after a peer is killed When a peer is killed and is later restarted, then any attempt to query anything from it using restconf will lead to a bunch of warnings about a dead connection. After digging in the RequestsLibrary source I realized that the proper cure is to tell the RequestsLibrary.Create_Session to not make any retries if the first connection attempt fails. Change-Id: Ic0586a280d2d9bda675771182f66374c4c6cd982 Signed-off-by: Jozef Behran --- csit/libraries/ClusterManagement.robot | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/csit/libraries/ClusterManagement.robot b/csit/libraries/ClusterManagement.robot index ed3979a101..f2759e1f29 100644 --- a/csit/libraries/ClusterManagement.robot +++ b/csit/libraries/ClusterManagement.robot @@ -239,5 +239,5 @@ ClusterManagement__Include_Member_Index Collections.Set_To_Dictionary ${index_to_ip_mapping} ${index} ${member_ip} # Http session, with ${AUTH}, without headers. ${session_alias} = Resolve_Http_Session_For_Member member_index=${index} - RequestsLibrary.Create_Session ${session_alias} http://${member_ip}:${RESTCONFPORT} auth=${AUTH} + RequestsLibrary.Create_Session ${session_alias} http://${member_ip}:${RESTCONFPORT} auth=${AUTH} max_retries=0 Collections.Append_To_List ${session_list} ${session_alias} -- 2.36.6