HC Test: reenable TC12 from BGP suite

Crash on adding recoursive routes was fixed on VPP side (VPP-1084).

Change-Id: I7b104eb2324a16dc8c19addd295e32f718f5c9fa
Signed-off-by: Marek Gradzki <mgradzki@cisco.com>

diff --git a/tests/vpp/func/honeycomb/mgmt-cfg-bgp-apihc-func.robot b/tests/vpp/func/honeycomb/mgmt-cfg-bgp-apihc-func.robot
index 9d9c5ea..b5fed1e 100644 (file)
--- a/tests/vpp/func/honeycomb/mgmt-cfg-bgp-apihc-func.robot
+++ b/tests/vpp/func/honeycomb/mgmt-cfg-bgp-apihc-func.robot
@@ -230,8 +230,6 @@
 | | ... | [ver] Verify that the route is present in BGP
 | | ... | local RIB and VPP's routing table on each DUT.
 | | ...
 | | ... | [ver] Verify that the route is present in BGP
 | | ... | local RIB and VPP's routing table on each DUT.
 | | ...

-# HC2VPP-267: Adding IPv4 route via BGP crashes VPP
-| | [Tags] | EXPECTED_FAILING

 | | Given Peer operational data from Honeycomb should be
 | | ... | ${dut1_node} | ${dut2_to_dut1_ip}
 | | And Peer operational data from Honeycomb should be
 | | Given Peer operational data from Honeycomb should be
 | | ... | ${dut1_node} | ${dut2_to_dut1_ip}
 | | And Peer operational data from Honeycomb should be