Fix for VTN Manager Li job Failure

Removed the method to add flows for table miss,
it looks like Jenkins is using the OVS 2.0.1 for
Li jobs and this is not necessary.Retained the keyword
so that it can be used in the future

Change-Id: I7f8a6c03a29737dadbaae659fd7fd6b3fc9fe034
Signed-off-by: gvrangan <venkatrangang@hcl.com>

diff --git a/csit/libraries/VtnMaKeywordsLi.robot b/csit/libraries/VtnMaKeywordsLi.robot
index 76a2a196a88df660dd77f7a821b7a3e1ce070a5e..add2b11c0039bc43ff48bbd6b48201549e55a689 100644 (file)
--- a/csit/libraries/VtnMaKeywordsLi.robot
+++ b/csit/libraries/VtnMaKeywordsLi.robot
@@ -217,7 +217,6 @@ Add a vBridgeMacMapping
 Mininet Ping Should Succeed
     [Arguments]    ${host1}    ${host2}
     [Documentation]    Ping hosts to check connectivity
-    Run Keyword If    '${OPENFLOW_VERSION}' == 'OF13'    Add Table Miss Flows
     Write    ${host1} ping -c 1 ${host2}
     ${result}    Read Until    mininet>
     Should Contain    ${result}    64 bytes
@@ -225,7 +224,6 @@ Mininet Ping Should Succeed
 Mininet Ping Should Not Succeed
     [Arguments]    ${host1}    ${host2}
     [Documentation]    Ping hosts when there is no connectivity and check hosts is unreachable
-    Run Keyword If    '${OPENFLOW_VERSION}' == 'OF13'    Add Table Miss Flows
     Write    ${host1} ping -c 3 ${host2}
     ${result}    Read Until    mininet>
     Should Not Contain    ${result}    64 bytes