dimsumdev / cpd

Catch all of random Cloud Pak for Data technical items

For information on pods to thier related service (Core & KC)

pod service reference.md

IBM will no longer be supporting ZenHub Enterprise. Users should transition to Jira@IBM or GitHub Projects

ZenHub Enterprise Sunset

Connections for testing (IBM internal)

For IBM internal environments you may use the DataQuack service to validate access to various types of data sources. See table in README.md file for connection parameters. Supported data sources include:

• MongoDB
• Oracle
• MySQL
• MariaDB
• PostgreSQL
• Minio
• Db2
• Microsoft SQL Server
• Informix

cpd's Issues

3.5 - Global Connection - Experiencing issues when creating or testing

Perform the following tasks if you are experiencing issues when creating or testing global connections.

1. Check whether the connection type is supported.
2. Make sure that connection test is successful.

• Check logs of wdp-connect-connection and wdp-connect-connector pods for more information if it is not.

3. Eliminate network issues.

• Logon to CP4D worker node and check with command curl -k -v <host>:<port> whether database host and port are accessible.

4. Check whether the data source is up and running.
5. Validate connection parameters using a different tool.
   Ask client to use standard tooling for validating the access to the data source.

Connections for testing (IBM internal)

For IBM internal environments you may use the DataQuack service to validate access to various types of data sources. See table in README.md file for connection
parameters. Supported data sources include:

• MongoDB
• Oracle
• MySQL
• MariaDB
• PostgreSQL
• Minio
• Db2
• Microsoft SQL Server
• Informix

3.5 - No feedback from UI when trying to download diagnostic file

After creating a diagnostic file and starting the download, there is no feedback in the UI, i.e. no Window is popping up for selecting a download location. However, in the browser console, you can see that the download is already going on. But then, when in reaches 1 GB file size, it fails.

Steps to reproduce

1. Open the browser console.
2. Create a diagnostic job that covers a large time period so the file size will be greater than 1 GB. In our scenario, components WKC and CCS were selected with 30 min time period.
3. Wait for the job to complete, then select to download the diagnostic file.
4. There won't be any feedback in the UI.
5. Follow the activity in the browser console.
6. You see that the file is actually being processed but it fails when 1 GB file size is reached.

Workaround

The generated diagnostic file is located under user-home/serviceability/collectedLogs. The filename matches the ID associated with the diagnostics collection. To download it to your local node from user-home you can use the following command. Replace by the name of the OpenShift namespace in which CP4D was installed.

oc cp <namespace>/<nginx_pod>:/user-home/serviceability/<job_id>.zip <destination>

3.5 - Known issues related to gathering diagnostics

Known issues related to gathering diagnostics

Problem	Error message or symptom
Error 400 when gathering diagnostic job for Common Core Services (CCS) component	Http error 400
Error 500 when gathering diagnostic job for Common Core Services (CCS) component	Http error 500
Error 504 when gathering diagnostics	Http error 504
No feedback from UI when trying to download large diagnostic files	No response from UI.

3.5 - Debug LDAP Config

enable debug :

oc set env Deployment/usermgmt DEBUG="*"
oc scale deploy usermgmt --replicas=1

repeat the problem, collect logs of usermgmt pod. Then restore the default configuration:

oc set env Deployment/usermgmt DEBUG=""
oc scale deploy usermgmt --replicas=2

3.5 - Knowledge Catalog (IKC / WKC) - Architecture for related Pods