aboutsummaryrefslogtreecommitdiffstats
path: root/docs/report/honeycomb_functional_tests
diff options
context:
space:
mode:
authorVratko Polak <vrpolak@cisco.com>2018-07-09 15:14:36 +0200
committerPeter Mikus <pmikus@cisco.com>2018-07-10 11:23:31 +0000
commit61ef529d33efd51acd1b1986c325d25a9d7ba705 (patch)
treecbb5ab397295053934160102dc62aea4d53da939 /docs/report/honeycomb_functional_tests
parent173a910c5f56106cd5aaa620ae0f9cfb94fcfac3 (diff)
Remove THIS tag and use unix endlines
The THIS tag has sneaked in 10Ge2P1X520-Eth-L2Xcbase-Eth-1Memif-1Dcr-Mrr but usually it is only to be used in draft testing. Not sure about the way non-unix endlines crept in. Is not git supposed to perform endline conversions on text files? Or are .robot, .rst, .yaml and .vat not recognized as text? Change-Id: Ia78cf942c05c3029c340a8639782786f37e57469 Signed-off-by: Vratko Polak <vrpolak@cisco.com>
Diffstat (limited to 'docs/report/honeycomb_functional_tests')
-rw-r--r--docs/report/honeycomb_functional_tests/csit_release_notes.rst62
-rw-r--r--docs/report/honeycomb_functional_tests/documentation.rst10
-rw-r--r--docs/report/honeycomb_functional_tests/test_environment.rst10
3 files changed, 41 insertions, 41 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. |
++---+--------------------------------------------+---------------+-------------------------------------------------------------------------+
diff --git a/docs/report/honeycomb_functional_tests/documentation.rst b/docs/report/honeycomb_functional_tests/documentation.rst
index 7ded3d4181..354c4062f6 100644
--- a/docs/report/honeycomb_functional_tests/documentation.rst
+++ b/docs/report/honeycomb_functional_tests/documentation.rst
@@ -1,5 +1,5 @@
-Documentation
-=============
-
-`CSIT Honeycomb Functional Tests Documentation`_ contains detailed
-functional description and input parameters for each test case.
+Documentation
+=============
+
+`CSIT Honeycomb Functional Tests Documentation`_ contains detailed
+functional description and input parameters for each test case.
diff --git a/docs/report/honeycomb_functional_tests/test_environment.rst b/docs/report/honeycomb_functional_tests/test_environment.rst
index 8f7e7efa51..8d8d832e92 100644
--- a/docs/report/honeycomb_functional_tests/test_environment.rst
+++ b/docs/report/honeycomb_functional_tests/test_environment.rst
@@ -1,5 +1,5 @@
-Test Environment
-================
-
-CSIT functional tests are currently executed in FD.IO VIRL testbed.
-See `VPP Functional Tests Environment <../vpp_functional_tests/test_environment.html>`_ for more details.
+Test Environment
+================
+
+CSIT functional tests are currently executed in FD.IO VIRL testbed.
+See `VPP Functional Tests Environment <../vpp_functional_tests/test_environment.html>`_ for more details.