X-Git-Url: https://gerrit.fd.io/r/gitweb?p=csit.git;a=blobdiff_plain;f=tests%2Ffunc%2Fhoneycomb%2F010_interface_management.robot;h=2c639c5c6ac7d8c4fe252b3f39130dc54723f37c;hp=e9798167c77839665b001639f05ebaf3446a4da9;hb=19c91adadd57bfc4e7514993b2a711a826d52e04;hpb=c75b9804c9510d0a342563e41407089145b38d50 diff --git a/tests/func/honeycomb/010_interface_management.robot b/tests/func/honeycomb/010_interface_management.robot index e9798167c7..2c639c5c6a 100644 --- a/tests/func/honeycomb/010_interface_management.robot +++ b/tests/func/honeycomb/010_interface_management.robot @@ -33,16 +33,20 @@ *** Settings *** | Resource | resources/libraries/robot/default.robot | Resource | resources/libraries/robot/honeycomb/interfaces.robot +| Resource | resources/libraries/robot/honeycomb/honeycomb.robot | Force Tags | honeycomb_sanity +| Suite Teardown | Run Keyword If Any Tests Failed +| | ... | Restart Honeycomb And VPP And Clear Persisted Configuration | ${node} | Documentation | *Honeycomb interface management test suite.* | ... | ... | Test suite uses the first interface of the first DUT node. *** Test Cases *** +# TODO: Remove "continue on failure" once VPP bugs (VPP-132, VPP-333) are fixed. | Honeycomb configures and reads interface state | | [Documentation] | Check if Honeycomb API can modify the admin state of\ | | ... | VPP interfaces. -| | Given Interface state is | ${node} | ${interface} | down +| | Given Interface State Is | ${node} | ${interface} | down | | When Honeycomb sets interface state | ${node} | ${interface} | up | | Then Interface state from Honeycomb should be | | ... | ${node} | ${interface} | up @@ -59,22 +63,26 @@ | | ... | ${ipv4_address} | ${ipv4_mask} | ${ipv4_settings} | | And Honeycomb adds interface ipv4 neighbor | | ... | ${node} | ${interface} | @{ipv4_neighbor} -| | Then IPv4 config from Honeycomb should be +| | Run Keyword And Continue On Failure +| | ... | Then IPv4 config from Honeycomb should be | | ... | ${node} | ${interface} | ${ipv4_address} | ${ipv4_prefix} | | ... | @{ipv4_neighbor} | ${ipv4_settings} -| | And IPv4 config from VAT should be +| | Run Keyword And Continue On Failure +| | ... | And IPv4 config from VAT should be | | ... | ${node} | ${interface} | ${ipv4_address} | ${ipv4_prefix} | Honeycomb removes ipv4 address from interface | | [Documentation] | Check if Honeycomb API can remove configured ipv4\ | | ... | addresses from interface. -| | Given IPv4 config from Honeycomb should be +| | Run Keyword And Continue On Failure +| | ... | Given IPv4 config from Honeycomb should be | | ... | ${node} | ${interface} | ${ipv4_address} | ${ipv4_prefix} | | ... | @{ipv4_neighbor} | ${ipv4_settings} -| | And IPv4 config from VAT should be +| | Run Keyword And Continue On Failure +| | ... | And IPv4 config from VAT should be | | ... | ${node} | ${interface} | ${ipv4_address} | ${ipv4_prefix} | | When Honeycomb removes interface ipv4 addresses | ${node} | ${interface} -| | Then IPv4 address from Honeycomb should be empty | ${node} |${interface} +| | Then IPv4 address from Honeycomb should be empty | ${node} | ${interface} | | And ipv4 address from VAT should be empty | ${node} | ${interface} | Honeycomb modifies interface configuration - ipv4 (prefix) @@ -87,11 +95,13 @@ | | ... | ${ipv4_settings} | | And Honeycomb adds interface ipv4 neighbor | | ... | ${node} | ${interface} | @{ipv4_neighbor} -| | Then IPv4 config from Honeycomb should be +| | Run Keyword And Continue On Failure +| | ... | Then IPv4 config from Honeycomb should be | | ... | ${node} | ${interface} | ${ipv4_address2} | ${ipv4_prefix} | | ... | @{ipv4_neighbor} | | ... | ${ipv4_settings} -| | And IPv4 config from VAT should be +| | Run Keyword And Continue On Failure +| | ... | And IPv4 config from VAT should be | | ... | ${node} | ${interface} | ${ipv4_address2} | ${ipv4_prefix} | Honeycomb modifies interface configuration - ipv6 @@ -99,10 +109,12 @@ | | When Honeycomb sets interface ipv6 configuration | | ... | ${node} | ${interface} | @{ipv6_address} | @{ipv6_neighbor} | | ... | ${ipv6_settings} -| | Then IPv6 config from Honeycomb should be +| | Run Keyword And Continue On Failure +| | ... | Then IPv6 config from Honeycomb should be | | ... | ${node} | ${interface} | @{ipv6_address} | @{ipv6_neighbor} | | ... | ${ipv6_settings} -| | And IPv6 config from VAT should be +| | Run Keyword And Continue On Failure +| | ... | And IPv6 config from VAT should be | | ... | ${node} | ${interface} | @{ipv6_address} | Honeycomb modifies interface configuration - ethernet,routing