CSIT-1213: Add 2n/3n-skx to Test Oper Data

[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 68b5eb6..21e2c6a 100644 (file)
--- a/docs/report/honeycomb_functional_tests/csit_release_notes.rst
+++ b/docs/report/honeycomb_functional_tests/csit_release_notes.rst
@@ -1,35 +1,31 @@
-CSIT Release Notes\r
-==================\r
-\r
-Changes in CSIT |release|\r
--------------------------\r
-\r
-#. Naming change for all Honeycomb functional test suites in VIRL\r
-\r
-    - Honeycomb functional test case names stayed unchanged\r
-\r
-#. Added Honeycomb functional tests\r
-\r
-    - NSH_SFC\r
-    - LISP\r
-    - NAT\r
-    - SPAN\r
-\r
-Known Issues\r
-------------\r
-\r
-Here is the list of known issues in CSIT |release| for Honeycomb functional\r
-tests in VIRL:\r
-\r
-+---+-------------------------------------------------+-----------------------------------------------------------------+\r
-| # | Issue                                           | Description                                                     |\r
-+---+-------------------------------------------------+-----------------------------------------------------------------+\r
-| 1 | Operational data for Vhost-user interfaces      | Honeycomb Operational data reports Vhost-user interfaces        |\r
-|   | "server" flag                                   | as client, even if they are server.                             |\r
-+---+-------------------------------------------------+-----------------------------------------------------------------+\r
-| 2 | Persistence of VxLAN tunnels                    | Configuration persistence often fails to restore                |\r
-|   |                                                 | Honeycomb's internal naming context for VxLAN interfaces.       |\r
-|   |                                                 | The interface is renamed to "vxlan_tunnel0" but is otherwise    |\r
-|   |                                                 | configured correctly.                                           |\r
-+---+-------------------------------------------------+-----------------------------------------------------------------+\r
-\r
+Release Notes
+=============
+
+Changes in |csit-release|
+-------------------------
+
+No changes.
+
+Known Issues
+------------
+
+Here is the list of known issues in |csit-release| for Honeycomb functional
+tests in VIRL:
+
++---+--------------------------------------------+---------------+-------------------------------------------------------------------------+
+| # | Issue                                      | Jira ID       | Description                                                             |
++---+--------------------------------------------+---------------+-------------------------------------------------------------------------+
+| 1 | IPv6 BGP route configuration               | HONEYCOMB-403 | Configuring Ipv6 route results in missing writer                        |
+|   |                                            |               | for IPv6Route and IPv6NextHop exception.                                |
++---+--------------------------------------------+---------------+-------------------------------------------------------------------------+
+| 2 | IP address subnet validation               | VPP-649       | When configuring two IP addresses from the same subnet on an interface, |
+|   |                                            |               | VPP refuses the configuration but returns code 200:OK. This can cause   |
+|   |                                            |               | desync between Honeycomb's config and operational data.                 |
++---+--------------------------------------------+---------------+-------------------------------------------------------------------------+
+| 3 | VxLAN GPE configuration crashes VPP        | VPP-875       | Specific VxLAN GPE configurations cause VPP to crash and restart.       |
++---+--------------------------------------------+---------------+-------------------------------------------------------------------------+
+| 4 | Operational data for IPv6 special routes   | HC2VPP-254    | Special hop routes are misidentified as regular routes                  |
+|   |                                            |               | in operational data.                                                    |
++---+--------------------------------------------+---------------+-------------------------------------------------------------------------+
+| 5 | LISP PITR feature configuration            | HC2VPP-263    | Locator set reference in operational data is incorrect.                 |
++---+--------------------------------------------+---------------+-------------------------------------------------------------------------+