Remove check for leadership change

see [0] for more details, but the idea is that we
have some sporadic cases where the isolated node
will report a node unreachable while it's being
rejoined to the cluster which triggers a new leader
election. This unreachable node messages can be
expected if the timing of things is a certain way
so the new leader election is also expected. In
the spirit of creating stable CSIT results without
sporadic failures, we will remove this test case.

[0] https://jira.opendaylight.org/browse/CONTROLLER-1865

JIRA: CONTROLLER-1865
Change-Id: Ic5da2d0748915a36e11eaa841f4b2772ecf7540f
Signed-off-by: Jamo Luhrsen <jluhrsen@redhat.com>

diff --git a/csit/suites/controller/singleton_service/global_rpc_isolate.robot b/csit/suites/controller/singleton_service/global_rpc_isolate.robot
index 1d820af1eedc123c82a6c05b3967e39379bf352c..489544107c5595cce817f3b61b610572c872975f 100644 (file)
--- a/csit/suites/controller/singleton_service/global_rpc_isolate.robot
+++ b/csit/suites/controller/singleton_service/global_rpc_isolate.robot
@@ -73,10 +73,6 @@ Rejoin_Isolated_Member
     ClusterManagement.Rejoin_Member_From_List_Or_All    ${old_brt_owner}
     BuiltIn.Wait_Until_Keyword_Succeeds    70s    10s    ShardStability.Shards_Stability_Get_Details    ${DEFAULT_SHARD_LIST}
 
-Verify_New_Owner_Remained_After_Rejoin
-    [Documentation]    Verify no owner change happened after rejoin.
-    WaitForFailure.Verify_Keyword_Does_Not_Fail_Within_Timeout    15s    2s    Verify_Owner_Elected    ${False}    ${brt_owner}    ${brt_owner}
-
 Rpc_After_Rejoin_On_New_Owner
     [Documentation]    Run rpc on the new service owner node.
     Run_Rpc    ${brt_owner}