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
+No changes.\r
\r
Known Issues\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
++---+--------------------------------------------+---------------+-------------------------------------------------------------------------+\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