diff options
author | selias <samelias@cisco.com> | 2017-04-25 09:22:58 +0200 |
---|---|---|
committer | Peter Mikus <pmikus@cisco.com> | 2017-04-25 08:50:08 +0000 |
commit | b4a288b19aa838825eff803207d1fedd82cb62f3 (patch) | |
tree | 341ae6dd3cc84f9c1320a05511e121b9bc0f1345 /docs/report/honeycomb_functional_tests/csit_release_notes.rst | |
parent | e96838cfbc9a742a7c543a1b88a2d4d2eaf5d08b (diff) |
1704 Report - Honeycomb section
Change-Id: I8006cf8187f943b8d880c8193b6b1bde25ad343c
Signed-off-by: selias <samelias@cisco.com>
Diffstat (limited to 'docs/report/honeycomb_functional_tests/csit_release_notes.rst')
-rw-r--r-- | docs/report/honeycomb_functional_tests/csit_release_notes.rst | 44 |
1 files changed, 25 insertions, 19 deletions
diff --git a/docs/report/honeycomb_functional_tests/csit_release_notes.rst b/docs/report/honeycomb_functional_tests/csit_release_notes.rst index 68b5eb6fb5..52525423f6 100644 --- a/docs/report/honeycomb_functional_tests/csit_release_notes.rst +++ b/docs/report/honeycomb_functional_tests/csit_release_notes.rst @@ -4,32 +4,38 @@ CSIT Release Notes Changes in CSIT |release|
-------------------------
-#. Naming change for all Honeycomb functional test suites in VIRL
-
- - Honeycomb functional test case names stayed unchanged
-
#. Added Honeycomb functional tests
- - NSH_SFC
- - LISP
- - NAT
- - SPAN
+ - ACL plugin
+ - Routing
+ - SLAAC
+ - Proxy ARP
+ - DHCP Relay
+ - Neighbor Discovery Proxy
+
+#. Changed execution environment from Ubuntu14.04 to Ubuntu16.04
Known Issues
------------
Here is the list of known issues in CSIT |release| for Honeycomb functional
tests in VIRL:
++---+--------------------------------------------+------------+----------------------------------------------------------------------------+
+| # | Issue | Jira ID | Description |
++---+--------------------------------------------+------------+----------------------------------------------------------------------------+
+| 1 | IP address subnet validation | VPP-649 | When configuring two IP addresses from the same subnet on an interface, |
+| | | | VPP refuses the configuration but returns OK. This can cause desync |
+| | | | between Honeycomb's config and operational data. |
++---+--------------------------------------------+------------+----------------------------------------------------------------------------+
+| 2 | Persistence of VxLAN tunnel naming context | HC2VPP-47 | When VPP restarts with Honeycomb running and a VxLan interface configured, |
+| | | | the interface is sometimes renamed to "vxlan_tunnel0". |
+| | | | It is otherwise configured correctly. |
++---+--------------------------------------------+------------+----------------------------------------------------------------------------+
+| 3 | Classifier plugin for IPv6 cases | VPP-687 | Classifier ignores IPv6 packets with less than 8 bytes after last header. |
+| | | | Fixed in VPP 17.07. |
++---+--------------------------------------------+------------+----------------------------------------------------------------------------+
+| 4 | Batch disable Lisp features | HC2VPP-131 | When removing complex Lisp configurations in a single request, |
+| | | | the operation fails due to a write ordering issue. |
++---+--------------------------------------------+------------+----------------------------------------------------------------------------+
-+---+-------------------------------------------------+-----------------------------------------------------------------+
-| # | Issue | Description |
-+---+-------------------------------------------------+-----------------------------------------------------------------+
-| 1 | Operational data for Vhost-user interfaces | Honeycomb Operational data reports Vhost-user interfaces |
-| | "server" flag | as client, even if they are server. |
-+---+-------------------------------------------------+-----------------------------------------------------------------+
-| 2 | Persistence of VxLAN tunnels | Configuration persistence often fails to restore |
-| | | Honeycomb's internal naming context for VxLAN interfaces. |
-| | | The interface is renamed to "vxlan_tunnel0" but is otherwise |
-| | | configured correctly. |
-+---+-------------------------------------------------+-----------------------------------------------------------------+
|