summaryrefslogtreecommitdiffstats
path: root/docs/sections/services/pm-subscription-handler/troubleshooting.rst
diff options
context:
space:
mode:
authorefiacor <fiachra.corcoran@est.tech>2021-02-09 16:02:02 +0000
committerefiacor <fiachra.corcoran@est.tech>2021-02-09 16:05:03 +0000
commit6132c206cc4a64df2248647326d569393605cf90 (patch)
tree53227fbacf486f1672361f0b761342dd951d5352 /docs/sections/services/pm-subscription-handler/troubleshooting.rst
parentfbcf2ebf0d02272c65277e1bd582b5ed132e6f77 (diff)
[PMSH] Add doc updates for update sub use case
Signed-off-by: efiacor <fiachra.corcoran@est.tech> Change-Id: Ibdaf35b844e0dff1fc035173888ab06dcf4e2dd4 Issue-ID: DCAEGEN2-2152
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, 13 insertions, 2 deletions
diff --git a/docs/sections/services/pm-subscription-handler/troubleshooting.rst b/docs/sections/services/pm-subscription-handler/troubleshooting.rst
index 8fe3034f..1c1a5a89 100644
--- a/docs/sections/services/pm-subscription-handler/troubleshooting.rst
+++ b/docs/sections/services/pm-subscription-handler/troubleshooting.rst
@@ -14,10 +14,21 @@ 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 logs in Kibana.
+see an error connecting to Config Binding Service, by checking the container logs.
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 Kibana for an incorrect configuration error.
+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