Set bgp longevity to run on rib owner node

Change-Id: I7fe6eab42835da24ba52b10c4d86a09df580773f
Signed-off-by: Peter Gubka <pgubka@cisco.com>

diff --git a/csit/suites/bgpcep/bgpclustering/singlepeer_pc_shm_300kroutes_longevity.robot b/csit/suites/bgpcep/bgpclustering/singlepeer_pc_shm_300kroutes_longevity.robot
index f6e83792561a0bc02d26af44711a207a3d0ca1b8..e04efb73d3ee01b75c0a4b7f80b4075f9c764a73 100644 (file)
--- a/csit/suites/bgpcep/bgpclustering/singlepeer_pc_shm_300kroutes_longevity.robot
+++ b/csit/suites/bgpcep/bgpclustering/singlepeer_pc_shm_300kroutes_longevity.robot
@@ -41,6 +41,7 @@ ${DURATION_24_HOURS_IN_SECONDS}    86400
 Configure_Prefixes_Longevity
     [Documentation]    Configure bgp peer, repeat the test scenario for 24h and deconfigure it.
     ${rib_owner}    ${rib_candidates}=    ClusterManagement.Get_Owner_And_Successors_For_device    example-bgp-rib    org.opendaylight.mdsal.ServiceEntityType    1
+    PrefixcountKeywords.Set_Shard_Leaders_Location_And_Verify    ${rib_owner}
     BuiltIn.Wait_Until_Keyword_Succeeds    ${INITIAL_RESTCONF_TIMEOUT}    1s    Check_For_Empty_Ipv4_Topology_On_All_Nodes
     &{mapping}    BuiltIn.Create_Dictionary    DEVICE_NAME=${DEVICE_NAME}    BGP_NAME=${BGP_PEER_NAME}    IP=${TOOLS_SYSTEM_IP}    HOLDTIME=${HOLDTIME}    PEER_PORT=${BGP_TOOL_PORT}
     ...    INITIATE=false    BGP_RIB=${RIB_INSTANCE}    PASSIVE_MODE=true    BGP_RIB_OPENCONFIG=${PROTOCOL_OPENCONFIG}