Fix OFP cluster test after OF code change

Change-Id: I7820e67d2ac46fd8bc955f353c0ad4d9a87a5b42
Signed-off-by: Luis Gomez <ecelgp@gmail.com>

diff --git a/csit/suites/openflowplugin/EntityOwnership/030_Cluster_Sync_Problems.robot b/csit/suites/openflowplugin/EntityOwnership/030_Cluster_Sync_Problems.robot
index 7b979deb2d54c800e0e1002611c0dc102c1efffe..0688791d4fb7a848bc656b84beaff4eae37e4be4 100644 (file)
--- a/csit/suites/openflowplugin/EntityOwnership/030_Cluster_Sync_Problems.robot
+++ b/csit/suites/openflowplugin/EntityOwnership/030_Cluster_Sync_Problems.robot
@@ -159,8 +159,8 @@ Check No Device Owners In Controller
     ${data} =    TemplatedRequests.Get_As_Json_From_Uri    uri=${ENTITY_OWNER_URI}    session=${session}
     #ofp-topology-manager entity is introduced in the OPNFLWPLUG-1022 bug fix, and this entity will
     #always be present in the EOS output. All 3 controller nodes will be candidate, so EOS output will
-    #contain 3 members.
-    BuiltIn.Should Contain X Times    ${data}    member    3
+    #contain 6 members (members show 2 times).
+    BuiltIn.Should Contain X Times    ${data}    member    6
 
 Verify New Master Controller Node
     [Arguments]    ${switch_name}    ${old_master}