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>

diff --git a/csit/suites/ovsdb/Southbound_Domain/Bug_Validation.robot b/csit/suites/ovsdb/Southbound_Domain/Bug_Validation.robot
index f49c139765ed126ccdb96c4d5c00b6e9fb716ba9..3fb35b390c4dbeadab21289519625876b89849dd 100644 (file)
--- 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"}