In case of ovsdb -all job, topology tree will have 69/53169/1
authorAnil Vishnoi <vishnoianil@gmail.com>
Sat, 11 Mar 2017 03:18:08 +0000 (19:18 -0800)
committerAnil Vishnoi <vishnoianil@gmail.com>
Sat, 11 Mar 2017 03:18:10 +0000 (19:18 -0800)
commitb17fb8d0cf1984a80643da3186a1e7d3eb4ce673
treed5c243288791fdf3f282c9add69961be4a8e09e8
parent651e139b0fa0996b8c924cfab64fe6301df8c0f7
In case of ovsdb -all job, topology tree will have
multiple topology in the config and operational data store
because multiple features are installed and most of the features
like bgp,netconf,hwvtep:1,sxp will initialize their topology.
So matching on {network-topology:{topology:[{topology-id:ovsdb:1}]}}
for checking if ovsdb:1 topology is empty will always fail.
We should only check if the ovsdb:1 topology is empty or not.
This patch fixes the matching issue.

Change-Id: Id37e62c30e02ebb0299d284261ec029072a255ce
Signed-off-by: Anil Vishnoi <vishnoianil@gmail.com>
csit/suites/ovsdb/Southbound_Domain/Bug_Validation.robot