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 <jbehran@cisco.com>

diff --git a/csit/libraries/ClusterManagement.robot b/csit/libraries/ClusterManagement.robot
index ed3979a101ea6bac3521d3c5e5dda2bdf0880e7c..f2759e1f29e14b054a48f759e6b89641c823c269 100644 (file)
--- 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}