aboutsummaryrefslogtreecommitdiffstats
path: root/tests/honeycomb
diff options
context:
space:
mode:
authorMichal Cmarada <mcmarada@cisco.com>2019-04-09 08:12:05 +0200
committerMichal Cmarada <mcmarada@cisco.com>2019-04-09 08:12:05 +0200
commit40f43968c59bfc40d899cb87bc454af442f17191 (patch)
treeee49144208fdb92c0d70fce00cc88f4a76f624b7 /tests/honeycomb
parentaa25184f3f0925b789de52296053dd51e2bf8684 (diff)
update tests after ODL bump to Neon
Change-Id: Ia733ad304c51b28f2a945e570120821254077189 Signed-off-by: Michal Cmarada <mcmarada@cisco.com>
Diffstat (limited to 'tests/honeycomb')
-rw-r--r--tests/honeycomb/func/mgmt-cfg-bgp-apihc-func.robot14
1 files changed, 7 insertions, 7 deletions
diff --git a/tests/honeycomb/func/mgmt-cfg-bgp-apihc-func.robot b/tests/honeycomb/func/mgmt-cfg-bgp-apihc-func.robot
index d4182018e9..8cf7a7cf31 100644
--- a/tests/honeycomb/func/mgmt-cfg-bgp-apihc-func.robot
+++ b/tests/honeycomb/func/mgmt-cfg-bgp-apihc-func.robot
@@ -118,7 +118,7 @@
| | ... | ${node} | ${address_internal} | ${route_data_ipv4}
| | ... | ${route_address_ipv4} | ${route_id_ipv4} | ipv4
| | Then BGP Route from Honeycomb should be
-| | ... | ${node} | ${address_internal} | ${route_data_ipv4}
+| | ... | ${node} | ${address_internal} | ${route_data_ipv4_oper}
| | ... | ${route_address_ipv4} | ${route_id_ipv4} | ipv4
| TC07: Honeycomb removes IPv4 route configuration
@@ -127,11 +127,11 @@
| | Given BGP peer from Honeycomb should be
| | ... | ${node} | ${address_internal} | ${peer_internal}
| | And BGP Route from Honeycomb should be
-| | ... | ${node} | ${address_internal} | ${route_data_ipv4}
+| | ... | ${node} | ${address_internal} | ${route_data_ipv4_oper}
| | ... | ${route_address_ipv4} | ${route_id_ipv4} | ipv4
| | When Honeycomb removes BGP route | ${node} | ${address_internal}
| | ... | ${route_address_ipv4} | ${route_id_ipv4} | ipv4
-| | Then No BGP Routes Should be Configured
+| | Then No BGP Routes Should exist
| | ... | ${node} | ${address_internal} | ipv4
| TC08: Honeycomb updates existing IPv4 route using BGP
@@ -142,7 +142,7 @@
| | ...
| | Given BGP peer from Honeycomb should be
| | ... | ${node} | ${address_internal} | ${peer_internal}
-| | And No BGP Routes Should be Configured
+| | And No BGP Routes Should exist
| | ... | ${node} | ${address_internal} | ipv4
| | When Honeycomb configures BGP route
| | ... | ${node} | ${address_internal} | ${route_data_ipv4}
@@ -151,7 +151,7 @@
| | ... | ${node} | ${address_internal} | ${route_data_ipv4_update}
| | ... | ${route_address_ipv4} | ${route_id_ipv4} | ipv4
| | Then BGP Route from Honeycomb should be
-| | ... | ${node} | ${address_internal} | ${route_data_ipv4_update}
+| | ... | ${node} | ${address_internal} | ${route_data_ipv4_update_oper}
| | ... | ${route_address_ipv4} | ${route_id_ipv4} | ipv4
| TC09: Honeycomb configures a second IPv4 route
@@ -173,10 +173,10 @@
| | ... | ${node} | ${address_internal} | ${route_data_ipv4_2}
| | ... | ${route_address_ipv4_2} | ${route_id_ipv4_2} | ipv4
| | Then BGP Route from Honeycomb should be
-| | ... | ${node} | ${address_internal} | ${route_data_ipv4}
+| | ... | ${node} | ${address_internal} | ${route_data_ipv4_oper}
| | ... | ${route_address_ipv4} | ${route_id_ipv4} | ipv4
| | And BGP Route from Honeycomb should be
-| | ... | ${node} | ${address_internal} | ${route_data_ipv4_2}
+| | ... | ${node} | ${address_internal} | ${route_data_ipv4_2_oper}
| | ... | ${route_address_ipv4_2} | ${route_id_ipv4_2} | ipv4
| TC10: Honeycomb sends BGP OPEN messages to configured peer