summaryrefslogtreecommitdiffstats
path: root/docs/sections/services/pm-subscription-handler/troubleshooting.rst
diff options
context:
space:
mode:
authorVijay Venkatesh Kumar <vv770d@att.com>2021-03-03 16:40:47 +0000
committerGerrit Code Review <gerrit@onap.org>2021-03-03 16:40:47 +0000
commitc4e6a97015243fa5afea7f9cf3e14a8bd2414f40 (patch)
treefbefa5335ef2800c5599474faaaca065f8a625db /docs/sections/services/pm-subscription-handler/troubleshooting.rst
parent52bd6226d050a9c6eef27329bb516d24ea61be71 (diff)
parentc1e9c2f17ce8a9800e3a8b22068411258989d7ea (diff)
Merge "Revert "[PMSH] Add doc updates for update sub use case""
Diffstat (limited to 'docs/sections/services/pm-subscription-handler/troubleshooting.rst')
-rw-r--r--docs/sections/services/pm-subscription-handler/troubleshooting.rst15
1 files changed, 2 insertions, 13 deletions
diff --git a/docs/sections/services/pm-subscription-handler/troubleshooting.rst b/docs/sections/services/pm-subscription-handler/troubleshooting.rst
index 1c1a5a89..8fe3034f 100644
--- a/docs/sections/services/pm-subscription-handler/troubleshooting.rst
+++ b/docs/sections/services/pm-subscription-handler/troubleshooting.rst
@@ -14,21 +14,10 @@ Unable to connect to Config Binding Service
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The PMSH may not be able to reach the Config Binding Service. If this is the case you will be able to
-see an error connecting to Config Binding Service, by checking the container logs.
+see an error connecting to Config Binding Service, by checking the logs in Kibana.
Invalid Configuration
^^^^^^^^^^^^^^^^^^^^^
If the PMSH is able to connect to Config Binding Service, but is failing to start. It may be due to
-invalid configuration. Check the container logs for an incorrect configuration error.
-
-Failure to create/delete Subscription
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-If an error occurs when UN/LOCKING the administrativeState of the subscription, this may be due to a failure
-in one of the following ONAP services/applications. Check the logs of each to debug the issue.
-
-- dmaap-message-router
-- policy-apex-pdp
-- cds-blueprints-processor
-- sdnc
+invalid configuration. Check Kibana for an incorrect configuration error.