Allow connection to karaf port during suite setup 64/71164/3
authorTomas Jamrisko <tjamrisk@redhat.com>
Fri, 20 Apr 2018 11:58:31 +0000 (13:58 +0200)
committerJamo Luhrsen <jluhrsen@redhat.com>
Thu, 26 Apr 2018 17:26:09 +0000 (17:26 +0000)
Typical tripleo deployment doesn't allow external connections
to karaf consoles. As a result the setup and thus all the other
tests fail.

Change-Id: I7c3a87d7d3e0a54741f60f2a84671ff55a48d8b8
Signed-off-by: Tomas Jamrisko <tjamrisk@redhat.com>
csit/libraries/KarafKeywords.robot

index 49e8c3e3c65ba16ad64eda0a34feaf0ea821b9f4..e172b5dd9b06fab196c80b4cfdcc9cdc934653b7 100644 (file)
@@ -20,6 +20,7 @@ Setup_Karaf_Keywords
     [Arguments]    ${http_timeout}=${DEFAULT_TIMEOUT_HTTP}
     [Documentation]    Initialize ClusterManagement. Open ssh karaf connections to each ODL.
     ClusterManagement.ClusterManagement_Setup    http_timeout=${http_timeout}
+    ClusterManagement.Run_Bash_Command_On_List_Or_All    iptables -I INPUT -p tcp --dport ${KARAF_SHELL_PORT} -j ACCEPT; iptables-save
     BuiltIn.Comment    First connections to Karaf console may fail, so WUKS is used. TODO: Track as a Bug.
     : FOR    ${index}    IN    @{ClusterManagement__member_index_list}
     \    BuiltIn.Run_Keyword_And_Ignore_Error    BuiltIn.Wait_Until_Keyword_Succeeds    3s    1s    Open_Controller_Karaf_Console_On_Background    member_index=${index}