From 64064a52f0da9e56bd3e767bd0095337a1311b6b Mon Sep 17 00:00:00 2001 From: Peter Gubka Date: Sun, 7 May 2017 16:37:47 +0200 Subject: [PATCH] Remove invalid test case Invoking rpc hots several problems including aaa even local implementations is present. See comments 8207, 8214. Change-Id: Iee50c9a94bac6104f4d1b2aa0594b9754fa58790 Signed-off-by: Peter Gubka --- .../dom_rpc_broker/action_provider_partition_and_heal.robot | 6 ------ 1 file changed, 6 deletions(-) diff --git a/csit/suites/controller/dom_rpc_broker/action_provider_partition_and_heal.robot b/csit/suites/controller/dom_rpc_broker/action_provider_partition_and_heal.robot index e071c06163..493b40beac 100644 --- a/csit/suites/controller/dom_rpc_broker/action_provider_partition_and_heal.robot +++ b/csit/suites/controller/dom_rpc_broker/action_provider_partition_and_heal.robot @@ -53,12 +53,6 @@ Isolate_One_Node [Documentation] Isolate one node with registered rpc. ClusterManagement.Isolate_Member_From_List_Or_All ${isolated_idx} -Invoke_Rpc_On_Isolated_Node - [Documentation] Invoke rpc on isolated node. Because rpc is registered on this node, local constant - ... is expected. - BuiltIn.Pass_Execution Invoking rpc on isolated node has several problems, see bugs 8207, 8214. - BuiltIn.Wait_Until_Keyword_Succeeds 3x 2s Verify_Local_Rpc_Invoked ${isolated_idx} - Invoke_Rpc_On_Remaining_Nodes [Documentation] Invoke rpc on non-islolated nodes. As the only instance of rpc remained in the non-isolated ... cluster nodes, only this value is expected. -- 2.36.6