aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMarek Gradzki <mgradzki@cisco.com>2018-01-12 12:20:30 +0100
committerPeter Mikus <pmikus@cisco.com>2018-01-15 09:22:09 +0000
commite884873db54bd07ef4e8beecd2218630bb4dc088 (patch)
treee45d48750f7df23c0b41c6aeb2069c51f2ffa1c4
parent91d500d70469a9fc73d4904314441aeb64d68e4e (diff)
HC CSIT Report: update release notes
Change-Id: I0479b9f9328f87b43f4a0c77820419dec30afea6 Signed-off-by: Marek Gradzki <mgradzki@cisco.com>
-rw-r--r--docs/report/honeycomb_functional_tests/csit_release_notes.rst38
1 files changed, 18 insertions, 20 deletions
diff --git a/docs/report/honeycomb_functional_tests/csit_release_notes.rst b/docs/report/honeycomb_functional_tests/csit_release_notes.rst
index 7509ca5dd2..f47a15af5a 100644
--- 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|
-------------------------
-#. Added Honeycomb functional tests for the following areas:
-
- - LISP GPE
- - Honeycomb northbound interfaces over IPv6
- - Honeycomb implementation of ODL BGP
-
-#. Improved test coverage for the following features:
-
- - Vlan sub-interfaces
+No changes.
Known Issues
------------
@@ -20,14 +12,20 @@ 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 code 200:OK. This can cause |
-| | | | desync between Honeycomb's config and operational data. |
-+---+--------------------------------------------+------------+----------------------------------------------------------------------------+
-| 2 | VxLAN GPE configuration crashes VPP | VPP-875 | Specific VxLAN GPE configurations cause VPP to crash and restart. |
-+---+--------------------------------------------+------------+----------------------------------------------------------------------------+
-| 3 | Operational data for IPv6 special routes | HC2VPP-228 | Special hop routes are misidentified as regular routes in operational data.|
-+---+--------------------------------------------+------------+----------------------------------------------------------------------------+
++---+--------------------------------------------+---------------+-------------------------------------------------------------------------+
+| # | 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. |
++---+--------------------------------------------+---------------+-------------------------------------------------------------------------+