aboutsummaryrefslogtreecommitdiffstats
path: root/docs/report/honeycomb_functional_tests/csit_release_notes.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/report/honeycomb_functional_tests/csit_release_notes.rst')
-rw-r--r--docs/report/honeycomb_functional_tests/csit_release_notes.rst62
1 files changed, 31 insertions, 31 deletions
diff --git a/docs/report/honeycomb_functional_tests/csit_release_notes.rst b/docs/report/honeycomb_functional_tests/csit_release_notes.rst
index f47a15af5a..c1c46ff9e7 100644
--- a/docs/report/honeycomb_functional_tests/csit_release_notes.rst
+++ b/docs/report/honeycomb_functional_tests/csit_release_notes.rst
@@ -1,31 +1,31 @@
-CSIT 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. |
-+---+--------------------------------------------+---------------+-------------------------------------------------------------------------+
+CSIT 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. |
++---+--------------------------------------------+---------------+-------------------------------------------------------------------------+