X-Git-Url: https://gerrit.fd.io/r/gitweb?a=blobdiff_plain;f=docs%2Freport%2Fhoneycomb_functional_tests%2Fcsit_release_notes.rst;h=7509ca5dd2fa16ea60647cb81b0da02a1f617bdf;hb=8685fb21ff141ef8159dbad0db37cc0e34aeb593;hp=52525423f6cd97583acf22ba85f820064f9fc2b1;hpb=b4a288b19aa838825eff803207d1fedd82cb62f3;p=csit.git

diff --git a/docs/report/honeycomb_functional_tests/csit_release_notes.rst b/docs/report/honeycomb_functional_tests/csit_release_notes.rst
index 52525423f6..7509ca5dd2 100644
--- a/docs/report/honeycomb_functional_tests/csit_release_notes.rst
+++ b/docs/report/honeycomb_functional_tests/csit_release_notes.rst
@@ -4,38 +4,30 @@ CSIT Release Notes
 Changes in CSIT |release|
 -------------------------
 
-#. Added Honeycomb functional tests
+#. Added Honeycomb functional tests for the following areas:
 
-    - ACL plugin
-    - Routing
-    - SLAAC
-    - Proxy ARP
-    - DHCP Relay
-    - Neighbor Discovery Proxy
+   - LISP GPE
+   - Honeycomb northbound interfaces over IPv6
+   - Honeycomb implementation of ODL BGP
 
-#. Changed execution environment from Ubuntu14.04 to Ubuntu16.04
+#. Improved test coverage for the following features:
+
+   - Vlan sub-interfaces
 
 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.                                      |
+|   |                                            |            | VPP refuses the configuration but returns code 200:OK. This can cause      |
+|   |                                            |            | desync between Honeycomb's config and operational data.                    |
 +---+--------------------------------------------+------------+----------------------------------------------------------------------------+
-| 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.                                                        |
+| 2 | VxLAN GPE configuration crashes VPP        | VPP-875    | Specific VxLAN GPE configurations cause VPP to crash and restart.          |
 +---+--------------------------------------------+------------+----------------------------------------------------------------------------+
-| 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.                         |
+| 3 | Operational data for IPv6 special routes   | HC2VPP-228 | Special hop routes are misidentified as regular routes in operational data.|
 +---+--------------------------------------------+------------+----------------------------------------------------------------------------+
-
-