Report: Add known issues to HoneyComb

Change-Id: I7ea5dbeb30b4343fc134bf3dd75d99837bf582df
Signed-off-by: Tibor Frank <tifrank@cisco.com>
Signed-off-by: Michal Cmarada <mcmarada@cisco.com>

diff --git a/docs/report/honeycomb_functional_tests/overview.rst b/docs/report/honeycomb_functional_tests/overview.rst
index 29bd671..2332169 100644 (file)
--- a/docs/report/honeycomb_functional_tests/overview.rst
+++ b/docs/report/honeycomb_functional_tests/overview.rst
@@ -86,7 +86,7 @@ virtual VM environment:
 |                       | - Netconf negative tests aimed at specific   |
 |                       |   issues.                                    |
 |                       | - Netconf/Restconf northbound over IPv6.     |
-|                       | - Test case count: 12.                       |
+|                       | - Test case count: 14.                       |
 +-----------------------+----------------------------------------------+
 | L2BD                  | - CRUD for L2 Bridge-Domain, interface       |
 |                       |   assignment.                                |
@@ -131,7 +131,7 @@ virtual VM environment:
 |                       |   interface.                                 |
 |                       | - Test case count: 6.                        |
 +-----------------------+----------------------------------------------+
-| NSH_SFC               | - CRD for NSH maps and entries, using        |
+| NSH_SFC (excluded)    | - CRD for NSH maps and entries, using        |
 |                       |   NSH_SFC plugin.                            |
 |                       | - Configure up to 2 NSH entries.             |
 |                       | - Configure up to 2 NSH maps.                |
@@ -211,7 +211,7 @@ virtual VM environment:
 |                       | - Test case count: 3.                        |
 +-----------------------+----------------------------------------------+
 
-Total 219 Honeycomb functional tests in the |csit-release|.
+Total 213 Honeycomb functional tests in the |csit-release|.
 
 Operational data in Honeycomb should mirror configuration data at all
 times. Because of this, test cases follow this general pattern: