Fix usage of executing command on remote system

- generic keyword vs mininet system specific

Change-Id: Ibe9db8d5d9310b4ec7db2ed725be99184834eb91
Signed-off-by: Kailash Khalasi <kailash.khalasi@gmail.com>

diff --git a/csit/suites/ovsdb/Southbound_Domain/010__configure_1_ovsdb_node.robot b/csit/suites/ovsdb/Southbound_Domain/010__configure_1_ovsdb_node.robot
index 00064d976dfbbaa789813a5f674dabed629ea93e..1af7400b4906ad8ee391535bca4e510fe7a67b25 100644 (file)
--- a/csit/suites/ovsdb/Southbound_Domain/010__configure_1_ovsdb_node.robot
+++ b/csit/suites/ovsdb/Southbound_Domain/010__configure_1_ovsdb_node.robot
@@ -20,8 +20,8 @@ ${QUEUE}          QUEUE-1
 
 *** Test Cases ***
 Make the OVS instance to listen for connection
-    Utils.Run Command On Remote System    ${TOOLS_SYSTEM_IP}    sudo ovs-vsctl del-manager
-    Utils.Run Command On Remote System    ${TOOLS_SYSTEM_IP}    sudo ovs-vsctl set-manager ptcp:${OVSDB_NODE_PORT}
+    Utils.Run Command On Mininet    ${TOOLS_SYSTEM_IP}    sudo ovs-vsctl del-manager
+    Utils.Run Command On Mininet    ${TOOLS_SYSTEM_IP}    sudo ovs-vsctl set-manager ptcp:${OVSDB_NODE_PORT}
 
 Connect to OVSDB Node
     [Documentation]    Initiate the connection to OVSDB node from controller