Verify the ovs manager is connected.

Change-Id: I5889ca1cea35b8b1e535774544117303081cd4be
Signed-off-by: Gabriel Robitaille-Montpetit <grmontpetit@inocybe.com>

diff --git a/test/csit/suites/ovsdb/Openstack_Neutron/001__connection_manager.robot b/test/csit/suites/ovsdb/Openstack_Neutron/001__connection_manager.robot
index 21372c8cba1072621cb7983f6e15c8f72d5df467..9bd24bfe268cafaf83b3a1a1d3e68b00e7f129bb 100644 (file)
--- a/test/csit/suites/ovsdb/Openstack_Neutron/001__connection_manager.robot
+++ b/test/csit/suites/ovsdb/Openstack_Neutron/001__connection_manager.robot
@@ -41,6 +41,14 @@ Make the OVS instance to listen for connection
     Should Not Contain    ${pingresult}    ${PING_NOT_CONTAIN}
     Wait Until Keyword Succeeds    8s    2s    Check For Elements At URI    ${OPERATIONAL_TOPO_API}    ${node_list}
 
+Get manager connection
+    [Documentation]    This will verify if the OVS manager is connected
+    [Tags]    OVSDB netvirt
+    ${output}    Run Command On Remote System    ${MININET}    sudo ovs-vsctl show
+    ${lines}=    Get Lines Containing String    ${output}    is_connected
+    ${manager}=    Get Line    ${lines}    0
+    Should Contain    ${manager}    true
+
 Get controller connection
     [Documentation]    This will make sure the controller is correctly set up/connected
     [Tags]    OVSDB netvirt