From 49a1894add0f6c9bb38d293c022f589958330c05 Mon Sep 17 00:00:00 2001 From: Olivier Dugeon Date: Fri, 13 Mar 2020 11:46:18 +0100 Subject: [PATCH] Update PCEP Path Computation Documentation Remove 'Known Bug' section in docs/pce/pcep-user-guide-path-computation.rst as bug has been resolved. JIRA: BGPCEP-898 Signed-off-by: Olivier Dugeon Change-Id: Iec633e7d7310f1cea3f62bc28639974d30b08774 --- .../pcep/pcep-user-guide-path-computation.rst | 40 ------------------- 1 file changed, 40 deletions(-) diff --git a/docs/pcep/pcep-user-guide-path-computation.rst b/docs/pcep/pcep-user-guide-path-computation.rst index 02006e3fad..610f149a9f 100644 --- a/docs/pcep/pcep-user-guide-path-computation.rst +++ b/docs/pcep/pcep-user-guide-path-computation.rst @@ -132,43 +132,3 @@ limitations mentioned hereinafter: All these limitations will be solved in future releases. -Known Bug -^^^^^^^^^ - -When using BGP-LS for automatic Graph topology acquisition, for an undetermined -reason, karaf is unable to start properly the *bgp-topology-provider* bundle. -This is due to karaf that doesn't properly manage blueprint dependencies. Thus, -BGP Topology Provider class is initialized with a wrong reference to the Graph -Topology Service: a null pointer is provided instead. However, it is easy to -overcome this issue by simply restarting the *bgp-topology-provider* bundle. - -First identify the bundle number of *bgp-topology-provider* and check the -status. - -.. code-block:: console - - opendaylight-user@karaf>bundle:list | grep bgp-topology-provider - 232 │ Failure │ 80 │ 0.14.0 │ bgp-topology-provider - - -Then restart the bundle if status is *Failure* - -.. code-block:: console - - opendaylight-user@karaf>bundle:restart 232 - -And finaly, verify that the bundle is active - -.. code-block:: console - - opendaylight-user@root>bundle:list 232 - START LEVEL 100 , List Threshold: 50 - ID │ State │ Lvl │ Version │ Name - ────┼────────┼─────┼─────────────────┼─────────────────────── - 232 │ Active │ 80 │ 0.14.0 │ bgp-topology-provider - - -Looking to the log, you will normally see that a new Graph has been created and -fulfil with your network topology element. Using Graph Rest API *Get Operational -Graph* will also validate that all is running correctly. - -- 2.36.6