Added a small testcase to debug the issue with testcase failures

Change-Id: I953d8916e9032bd6f6db6cb06f584b2a20457bbf
Signed-off-by: Chaudhry Muhammad Usama <chaudhryusama@gmail.com>

diff --git a/test/csit/suites/ovsdb/Southbound_Domain/010__configure_1_ovsdb_node.robot b/test/csit/suites/ovsdb/Southbound_Domain/010__configure_1_ovsdb_node.robot
index 86cfa0d2a8bed9a353e1fe67c37652b56218db2a..bd3722b0f06de1b5b72288a092d0afb994d2360b 100644 (file)
--- a/test/csit/suites/ovsdb/Southbound_Domain/010__configure_1_ovsdb_node.robot
+++ b/test/csit/suites/ovsdb/Southbound_Domain/010__configure_1_ovsdb_node.robot
@@ -123,6 +123,12 @@ Get Operational Topology to make sure the connection has been deleted
     @{list}    Create List    ovsdb://${MININET}:${OVSDB_PORT}
     Wait Until Keyword Succeeds    8s    2s    Check For Elements Not At URI    ${OPERATIONAL_TOPO_API}    ${list}
 
+Get Configuration Topology to make sure the connection has been deleted
+    [Documentation]    This request will fetch the configuration topology from the connected OVSDB nodes
+    [Tags]    Southbound
+    @{list}    Create List    ovsdb://${MININET}:${OVSDB_PORT}
+    Wait Until Keyword Succeeds    8s    2s    Check For Elements Not At URI    ${CONFIG_TOPO_API}    ${node_list}
+
 Reconnect to OVSDB Node
     [Documentation]    Initiate the connection to OVSDB node from controller
     [Tags]    Southbound