Fix for OPNFLWPLUG-1022 requires Topology Manager 93/75593/3
authorAnil Vishnoi <vishnoianil@gmail.com>
Thu, 30 Aug 2018 20:48:13 +0000 (13:48 -0700)
committerLuis Gomez <ecelgp@gmail.com>
Thu, 6 Sep 2018 15:29:20 +0000 (15:29 +0000)
commitffa04403057d7d354ca0a2261b6bc7eabf5aeb1d
treeef88301f7041974e38c8dc02018248337125e997
parent36f1d4cdc79940c94358065f999bc31537c029c1
Fix for OPNFLWPLUG-1022 requires Topology Manager

module to register for singleton clustering service.
That introduces application entity in the EOS output.
In the current cluster tests, after disconnecting all
the OpenFlow devices, test checks that no openflow
 device should have owner, by grepping the "member"
string, and expect that it should be 0. After
introducing topology manager entity, EOS output
will always have one entity with all the 3 controllers
as a candidates, so greppign the "member" string
will always return 3. This patch take care of this
change."

Change-Id: Id2d3c0905ec3cd02c2098c1c1aee61c081dfe629
Signed-off-by: Anil Vishnoi <vishnoianil@gmail.com>
csit/suites/openflowplugin/EntityOwnership/030_Cluster_Sync_Problems.robot