Known issues and limitations for Common core services

Data from a Presto connection takes a long time to load

Applies to: 5.1.0

If you connect to data with the Presto connection, it might take a long time to preview the data or to load the data into a tool like Data Refinery. The wait time can be as long as 30 seconds to a minute or more.

Workaround: You can configure a direct connection to the data source federated in Presto.

IBM watsonx.data Presto connection: Certain data types are not supported

Applies to: 5.1.0
Fixed in: 5.1.1

The IBM watsonx.data Presto connection does not support the following data types:

• FLOAT data types
• REAL
• SMALLINT
• TIME
• TINYINT

Error for Oracle connections when running queries that contain user-defined data types (UDTs)

Applies to: 5.1.0

If you run an SQL query on a table or a view with columns that contain user-defined data types (UDTs), you might receive an error that contains this message:

[IBM][Oracle JDBC Driver]User defined type not found

The driver requires access to the metadata associated with the user-defined type (UDT) during the query execution. If you only have the SELECT privilege for the table, but you do not have the corresponding privilege for the UDT, the driver cannot access the UDT's metadata.

Workaround: Grant the necessary privilege to the UDT. For example:
GRANT EXEC ON TYPE::[schema].[typename] TO [User];

Pods with dependency on common core services fail when the common core services are uninstalled and re-installed

Applies to: 5.1.0
Fixed in: 5.1.1

Problems may occur when you re-install a service with a dependency on the common core services after you uninstall the service by running the cpd-cli manage delete-cr command with the --include_dependency=true option.

Workaround:

1. Run the following command to check for pods in the Error state:

   oc get pod -n${PROJECT_CPD_INST_OPERANDS} |grep -v Completed |grep -v 1/1 |grep -v 2/2 |grep -v 3/3 |grep -v  4/4
   

2. Get the error log for one of the pods in the Error state:

   oc logs -f <pod-name>
   

3. Look for errors in the pods. The errors may show:

   * Connection #0 to host internal-nginx-svc.wkc.svc.cluster.local left intact
   Status code from call to create global asset type: 504
   

4. To delete the pods run:

   oc delete pods -n ${PROJECT_CPD_INST_OPERANDS} -l component=<pod-name>
   

CouchDB unexpectedly restarts in a non-FIPS environment

Applies to: 5.1.0

When running a cluster with CouchDB in a non-FIPS environment, the CouchDB container may unexpectedly restart. For example:

$ oc get pod -l app=couchdb
NAME            READY   STATUS    RESTARTS         AGE
wdp-couchdb-0   2/2     Running   12 (4m34s ago)   16m
wdp-couchdb-1   2/2     Running   10 (1m15s ago)   16m
wdp-couchdb-2   2/2     Running   2 (4m29s ago)    17m

Workaround: To fix this issue, run the following steps:

1. Access the namespace where IBM Knowledge Catalog is installed:

   $ oc project ${PROJECT_CPD_INST_OPERANDS}
   

2. Update the wdp-couchdb configmap to disable FIPS_mode, which is enabled by default:

   $ oc get configmap wdp-couchdb -o yaml | sed 's/fips_mode true/fips_mode false/' | oc apply -f -
   

3. Once the configmap is updated, conduct a rolling restart of the CouchDB pods:

   $ oc rollout restart sts wdp-couchdb
   

4. After all the CouchDB pods have restarted, place the common core services into maintenance mode to avoid the restarting issue being brought back by CCS reconciling:

   $ oc patch ccs ccs-cr --type merge --patch '{"spec": {"ignoreForMaintenance": true}}'
   

   You may see warning messages like the following when the change is applied:

   $ oc get configmap wdp-couchdb -o yaml | sed 's/fips_mode false/fips_mode true/' | oc apply -f -
   Warning: resource configmaps/wdp-couchdb is missing the kubectl.kubernetes.io/last-applied-configuration annotation which is required by oc apply. oc apply should only be used on resources created declaratively by either oc create --save-config or oc apply. The missing annotation will be patched automatically.
   configmap/wdp-couchdb configured
   

   This is to be expected and can be ignored, as long as the configmap was successfully configured and you can see a message like the following at the end of the warning message:

   configmap/wdp-couchdb configured
   

5. You can confirm that the changes have been made by running the following command, to confirm that fips_mode has been set to false:

   $ oc get configmap wdp-couchdb -o yaml |grep " -crypto fips_mode false"
    -crypto fips_mode false
   

Actions with a dependency on the common core services can fail if the global asset type definition update takes a long time to complete

Applies to: 5.1.0
Fixed in: 5.1.1

When you upgrade to IBM Software Hub Version 5.1.0, the metadata import service updates the global asset type definition. If your environment contains a large number of projects, it can take a long time for the global asset type definition to be updated. If you try to complete tasks that require the common core services, such as creating projects, before the update is complete, the request might fail.

In addition, if the update takes a long time, the common core services might generate multiple wkc-search-reindexing-resource-key-combined-job jobs. If there are too many wkc-search-reindexing-resource-key-combined-job jobs running concurrently, the update might take even longer.

Workaround: To help alleviate the slowness:

1. Check whether there are multiple wkc-search-reindexing-resource-key-combined-job jobs:

   oc get pod | grep wkc-search-reindexing-resource-key-combined-job | grep Running | wc -l
   

2. If there are multiple wkc-search-reindexing-resource-key-combined-job jobs, keep the oldest job and delete all of the newer jobs. To delete a job, run:

   oc delete job <job-name>
   

Ingesting data to default or externally added buckets by using watsonx.data Presto connector might fail

Applies to: 5.1.0

Ingesting data into default buckets or externally added buckets by using the watsonx.data Presto connector with the data policies defined in watsonx.data might fail.

Workaround: Use File connectors to ingest data into storage associated in watsonx.data.

For example, you can use Generic S3 connector to ingest data into any S3 compliant storage in watsonx.data, like Amazon S3 storage or IBM Cloud Object Storage.

Appended data by the IBM watsonx.data connector may not be immediately visible when running queries using the Presto engine

Applies to: 5.1.1

When appending data to a table created using the Presto engine, the appended rows may not be immediately visible when running read queries. This is because the Presto engine caches the state of the tables every two minutes by default.

Workaround
Run the following to fix this issue:

1. Modify the Presto config map on the OpenShift pod by running:

   oc edit cm <presto-config-map>
   

   For example:

   oc edit cm ibm-lh-lakehouse-presto-01-presto-config-cm-blue
   

2. Delete the following properties from the Presto config map:

   hive.metastore-cache-scope=ALL
   hive.metastore-cache-ttl=10m
   hive.metastore-refresh-interval=2m
   

   For example, the config map may show:

   LH_METASTORE_CACHE_ENABLED: "true"
   LH_METASTORE_CACHE_SCOPE: ALL
   LH_METASTORE_CACHE_TTL: 10m
   LH_METASTORE_REFRESH_INTERVAL: 2m
   

Cannot log out of Cloud Pak for Data from inside a dashboard

Applies to: 5.1.0, 5.1.1 and 5.1.2
Fixed in: 5.1.3

When you are logged in to the Cloud Pak for Data experience and have a dashboard open, you cannot log out of Cloud Pak for Data from the dashboard when you click your avatar in the toolbar and select Log out. There is no response from Cloud Pak for Data after you click Log out.

Workaround
To log out of Cloud Pak for Data, navigate to any page outside of the dashboard, then log out from this page:

1. Navigate to any page outside of the dashboard. For example, click IBM Cloud Pak for Data in the toolbar to go to the home page.

2. Click your avatar in the toolbar, then click Log out.

Disabling SSL certificate validation requires extra steps

If users want to explicitly disable the SSL certificate validation, users will have to perform extra steps to ensure that it has been disabled.

Procedure
When creating a new connection or editing an existing connection in the user interface:

1. Select the option to Validate the SSL certificate.
2. Unselect the option to Validate the SSL certificate.
3. Save the connection.

This will need to be performed for any connection where users want to disable the SSL certificate validation.

The watsonx.data and Presto connections do not work with specific data types

Applies to: 5.1.1

The watsonx.data Presto and Presto connections currently do not work with the following data types:

• TIME

The TIME and TIMESTAMP data types are not supported when the Presto C++ engine is used.

Parent topic: Service issues