diff options
author | Tony Hansen <tony@att.com> | 2021-03-03 16:32:04 +0000 |
---|---|---|
committer | Tony Hansen <tony@att.com> | 2021-03-03 16:32:04 +0000 |
commit | c1e9c2f17ce8a9800e3a8b22068411258989d7ea (patch) | |
tree | f6823c8aac6d3ea63cebe43b7f162751dc75956f /docs/sections/services/pm-subscription-handler/troubleshooting.rst | |
parent | 6132c206cc4a64df2248647326d569393605cf90 (diff) |
Revert "[PMSH] Add doc updates for update sub use case"
This reverts commit 6132c206cc4a64df2248647326d569393605cf90.
Reason for revert: Container not ready; functionality deferred to I release
Issue-ID: DCAEGEN2-2653
Issue-ID: DCAEGEN2-2152
Change-Id: I2ed41ce31d0b4e02e8e8a2faaffaef412d61b6d7
Signed-off-by: Tony Hansen <th1395@att.com>;
Diffstat (limited to 'docs/sections/services/pm-subscription-handler/troubleshooting.rst')
-rw-r--r-- | docs/sections/services/pm-subscription-handler/troubleshooting.rst | 15 |
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. |