From: Anil Vishnoi Date: Sat, 11 Mar 2017 03:18:08 +0000 (-0800) Subject: In case of ovsdb -all job, topology tree will have X-Git-Tag: release/boron-sr3~92 X-Git-Url: https://git.opendaylight.org/gerrit/gitweb?a=commitdiff_plain;h=b17fb8d0cf1984a80643da3186a1e7d3eb4ce673;p=integration%2Ftest.git 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 --- diff --git a/csit/suites/ovsdb/Southbound_Domain/Bug_Validation.robot b/csit/suites/ovsdb/Southbound_Domain/Bug_Validation.robot index f49c139765..3fb35b390c 100644 --- a/csit/suites/ovsdb/Southbound_Domain/Bug_Validation.robot +++ b/csit/suites/ovsdb/Southbound_Domain/Bug_Validation.robot @@ -191,5 +191,5 @@ Config and Operational Topology Should Be Empty ... topology data stores. Empty probably means that only ovsdb:1 is there. ${config_resp} RequestsLibrary.Get Request session ${CONFIG_TOPO_API} ${operational_resp} RequestsLibrary.Get Request session ${OPERATIONAL_TOPO_API} - Should Be Equal As Strings ${config_resp.content} {"network-topology":{"topology":[{"topology-id":"ovsdb:1"}]}} - Should Be Equal As Strings ${operational_resp.content} {"network-topology":{"topology":[{"topology-id":"ovsdb:1"}]}} + Should Contain ${config_resp.content} {"topology-id":"ovsdb:1"} + Should Contain ${operational_resp.content} {"topology-id":"ovsdb:1"}