From 61ef529d33efd51acd1b1986c325d25a9d7ba705 Mon Sep 17 00:00:00 2001 From: Vratko Polak Date: Mon, 9 Jul 2018 15:14:36 +0200 Subject: 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 --- .../csit_release_notes.rst | 62 +++++++++++----------- 1 file changed, 31 insertions(+), 31 deletions(-) (limited to '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 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. | ++---+--------------------------------------------+---------------+-------------------------------------------------------------------------+ -- cgit 1.2.3-korg