diff options
| author |   selias <samelias@cisco.com> | 2017-01-17 16:59:03 +0100 |
|---|---|---|
| committer |   Tibor Frank <tifrank@cisco.com> | 2017-01-27 11:44:14 +0000 |
| commit | a277b96ed799d9252ba9ca1deed4bda1fd026e88 (patch) | |
| tree | 1ebb6b1711e5a41db8169bdbbdf2eeb4190581a1 /tests/func/honeycomb/mgmt-cfg-lisp-apihc-apivat-func.robot | |
| parent | 9ca0843d56ea4dc9c1b24203d3542c983ede9e69 (diff) | |
CSIT-506: HC Test- Update and cleanup all suites
- remove EXPECTED_FAILING tag from IPv4 neighbor, IPv6 address, MTU
- fix bridge domain removal with interfaces assigned, it should fail
- fix teardown of L2 FIB suite (bridge domain removal, see above)
- disable vhost-user "server" test cases (VPP bug)
- fix keyword verifying sub-interface state
- update ACL test data (yang model changes)
- remove EXPECTED_FAILING tag from ACL table removal test
- update Jira IDs and comments in failing Lisp test case
- remove EXPECTED_FAILING tag from Lisp removal test case
- use vhost-user "client" instead of "server" in persistence tests
Change-Id: I32eafb6013b4512090c0d9365e10c61029179d49
Signed-off-by: selias <samelias@cisco.com>
Diffstat (limited to 'tests/func/honeycomb/mgmt-cfg-lisp-apihc-apivat-func.robot')
| -rw-r--r-- | tests/func/honeycomb/mgmt-cfg-lisp-apihc-apivat-func.robot | 14 |
1 files changed, 4 insertions, 10 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 5f602c5780..2356e8b00a 100644 --- a/tests/func/honeycomb/mgmt-cfg-lisp-apihc-apivat-func.robot +++ b/tests/func/honeycomb/mgmt-cfg-lisp-apihc-apivat-func.robot @@ -114,8 +114,6 @@ | TC08: Honeycomb configures Lisp mapping with adjacency | | [Documentation] | Check if Honeycomb can configure local and remote Lisp\ | | ... | mappings with VRF, and configure adjacency. -| | [Tags] | EXPECTED_FAILING -# Requests below "vrf-subtable" level fail on table-id lookup (HONEYCOMB-290) | | [Teardown] | Honeycomb removes all lisp mappings | ${node} | | Given Locator Set From Honeycomb Should Be | | ... | ${node} | ${interface} | ${locator_set} @@ -125,12 +123,11 @@ | | ... | ${node} | | And Lisp mappings from VAT should not exist | | ... | ${node} -| | And Honeycomb adds Lisp mapping | ${node} | ${lisp_settings_local_vrf} -| | And Honeycomb adds Lisp mapping | ${node} | ${lisp_settings_remote_vrf} -| | When Honeycomb adds Lisp adjacency | ${node} | ${4} | remote_map_vrf -| | ... | adj01 | ${remote_vrf_adjacency} +| | And Honeycomb adds Lisp mapping | ${node} | ${lisp_settings_both_vrf} +| | When Honeycomb adds Lisp adjacency | ${node} | ${7} | remote_map_vrf +| | ... | adj01 | ${vrf_adjacency} | | Then Lisp mapping from Honeycomb should be -| | ... | ${node} | ${remote_adj_subtable} +| | ... | ${node} | ${adj_subtable} | TC09: Honeycomb configures Lisp map resolver | | [Documentation] | Check if Honeycomb can configure a Lisp map resolver. @@ -150,9 +147,6 @@ | TC11: Honeycomb can remove configuration of Lisp features | | [Documentation] | Check if Honeycomb can disable all Lisp features. -| | [Tags] | EXPECTED_FAILING -# Delete operation fails due to incorrect write order(HONEYCOMB-296), -# but returns code 200: OK (HONEYCOMB-297) | | Given Map resolver from Honeycomb should be | ${node} | 192.168.0.4 | | And PITR config from Honeycomb should be | ${node} | ${locator_set} | | When Honeycomb disables all Lisp features | ${node} |