HC CSIT Report: update release notes

[csit.git] / docs / report / honeycomb_functional_tests / csit_release_notes.rst

diff --git a/docs/report/honeycomb_functional_tests/csit_release_notes.rst b/docs/report/honeycomb_functional_tests/csit_release_notes.rst
index 7509ca5..f47a15a 100644 (file)
--- a/docs/report/honeycomb_functional_tests/csit_release_notes.rst
+++ b/docs/report/honeycomb_functional_tests/csit_release_notes.rst
@@ -4,15 +4,7 @@ CSIT Release Notes
 Changes in CSIT |release|\r
 -------------------------\r
 \r
-#. Added Honeycomb functional tests for the following areas:\r
-\r
-   - LISP GPE\r
-   - Honeycomb northbound interfaces over IPv6\r
-   - Honeycomb implementation of ODL BGP\r
-\r
-#. Improved test coverage for the following features:\r
-\r
-   - Vlan sub-interfaces\r
+No changes.\r
 \r
 Known Issues\r
 ------------\r
@@ -20,14 +12,20 @@ Known Issues
 Here is the list of known issues in CSIT |release| for Honeycomb functional\r
 tests in VIRL:\r
 \r
-+---+--------------------------------------------+------------+----------------------------------------------------------------------------+\r
-| # | Issue                                      | Jira ID    | Description                                                                |\r
-+---+--------------------------------------------+------------+----------------------------------------------------------------------------+\r
-| 1 | IP address subnet validation               | VPP-649    | When configuring two IP addresses from the same subnet on an interface,    |\r
-|   |                                            |            | VPP refuses the configuration but returns code 200:OK. This can cause      |\r
-|   |                                            |            | desync between Honeycomb's config and operational data.                    |\r
-+---+--------------------------------------------+------------+----------------------------------------------------------------------------+\r
-| 2 | VxLAN GPE configuration crashes VPP        | VPP-875    | Specific VxLAN GPE configurations cause VPP to crash and restart.          |\r
-+---+--------------------------------------------+------------+----------------------------------------------------------------------------+\r
-| 3 | Operational data for IPv6 special routes   | HC2VPP-228 | Special hop routes are misidentified as regular routes in operational data.|\r
-+---+--------------------------------------------+------------+----------------------------------------------------------------------------+\r
++---+--------------------------------------------+---------------+-------------------------------------------------------------------------+\r
+| # | Issue                                      | Jira ID       | Description                                                             |\r
++---+--------------------------------------------+---------------+-------------------------------------------------------------------------+\r
+| 1 | IPv6 BGP route configuration               | HONEYCOMB-403 | Configuring Ipv6 route results in missing writer                        |\r
+|   |                                            |               | for IPv6Route and IPv6NextHop exception.                                |\r
++---+--------------------------------------------+---------------+-------------------------------------------------------------------------+\r
+| 2 | IP address subnet validation               | VPP-649       | When configuring two IP addresses from the same subnet on an interface, |\r
+|   |                                            |               | VPP refuses the configuration but returns code 200:OK. This can cause   |\r
+|   |                                            |               | desync between Honeycomb's config and operational data.                 |\r
++---+--------------------------------------------+---------------+-------------------------------------------------------------------------+\r
+| 3 | VxLAN GPE configuration crashes VPP        | VPP-875       | Specific VxLAN GPE configurations cause VPP to crash and restart.       |\r
++---+--------------------------------------------+---------------+-------------------------------------------------------------------------+\r
+| 4 | Operational data for IPv6 special routes   | HC2VPP-254    | Special hop routes are misidentified as regular routes                  |\r
+|   |                                            |               | in operational data.                                                    |\r
++---+--------------------------------------------+---------------+-------------------------------------------------------------------------+\r
+| 5 | LISP PITR feature configuration            | HC2VPP-263    | Locator set reference in operational data is incorrect.                 |\r
++---+--------------------------------------------+---------------+-------------------------------------------------------------------------+\r