aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorselias <samelias@cisco.com>2017-04-25 09:42:41 +0200
committerSamuel Eliáš <samelias@cisco.com>2017-04-25 07:43:33 +0000
commit16b8845485d9c6ae9fc01f3723a7cd90cb1cfbba (patch)
treeeed2c251356e6f0bb143f21abb10124a0bc21a05
parentd3eee64efbfbdc3bdfc86433341ad08c874407b4 (diff)
HC Test: add expected_failing tag to "disable_lisp" case
Change-Id: I614dea8d830e8bf97ac4b4ad24d21d3b707fae8a Signed-off-by: selias <samelias@cisco.com>
-rw-r--r--tests/func/honeycomb/mgmt-cfg-lisp-apihc-apivat-func.robot2
1 files changed, 2 insertions, 0 deletions
diff --git a/tests/func/honeycomb/mgmt-cfg-lisp-apihc-apivat-func.robot b/tests/func/honeycomb/mgmt-cfg-lisp-apihc-apivat-func.robot
index aeb4782d5c..18f9840341 100644
--- a/tests/func/honeycomb/mgmt-cfg-lisp-apihc-apivat-func.robot
+++ b/tests/func/honeycomb/mgmt-cfg-lisp-apihc-apivat-func.robot
@@ -146,6 +146,8 @@
| | And PITR config from VAT should be | ${node} | ${locator_set}
| TC11: Honeycomb can remove configuration of Lisp features
+| | [Tags] | EXPECTED_FAILING
+# HC2VPP-131 incorrect write order when removing Lisp configuration
| | [Documentation] | Check if Honeycomb can disable all Lisp features.
| | Given Map resolver from Honeycomb should be | ${node} | 192.168.0.4
| | And PITR config from Honeycomb should be | ${node} | ${locator_set}