Preventive Service Planning
Abstract
This document lists the available patches for IBM watsonx.data service.
Content
- Install watsonx.data on IBM Software Hub 5.2.0.
- Apply the patch for watsonx.data as described in this document.
Applying patch for watsonx.data
Air-gapped environment
- Log in to the OpenShift console as the cluster admin.
- Prepare the authentication credentials to access the IBM production repository. Use the same auth.json file used for CASE download and image mirroring. An example directory path:
Or create an auth.json file that contains credentials to access icr.io and your local private registry. For example:${HOME}/.airgap/auth.json
For more information about the auth.json file, see containers-auth.json - syntax for the registry authentication file.{ "auths": { "cp.icr.io":{"email":"unused","auth":"<base64 encoded id:apikey>"}, "<private registry hostname>":{"email":"unused","auth":"<base64 encoded id:password>"} } } - Install skopeo by running:
yum install skopeo - To confirm the path for the local private registry to copy the hotfix images, run the following command:
<hotfix image pod> can be the pod name for any of the images which will be patched with this hotfix.oc describe pod <hotfix image pod> | grep -i "image:"
For example:oc describe pod ibm-lh-lakehouse-presto-01-single-blue-0 | grep Image: … Image:cp.icr.io/cp/watsonx-data/ibm-lh-presto@sha256: 17fc47f1451485d883d8e9a7a8914c17b0b830867d1ab4a6d5c83a2c97d19f52 - To get the local private registry source details, run the following commands:
oc get imageContentSourcePolicy oc describe imageContentSourcePolicy [cloud-pak-for-data-mirror] - The local private registry mirror repository and path details should be in the output of the describe command:
- mirrors: - ${PRIVATE_REGISTRY_LOCATION}/cp/watsonx-data source: cp.icr.io/cp/watsonx-data
For more information about mirroring of images, see Configuring your cluster to pull Cloud Pak for Data images. - Use the skopeo command to copy the patch images from the IBM production registry to the local private registry. Using the appropriate auth.json file, copy the patch images from the IBM production registry to the OpenShift cluster registry:
NOTE: When copy/pasting each “skopeo” command below, it is recommended to copy the command into a text editor to ensure there are no additional newline characters after the ‘\’. Then copy/paste the command from the text editor to the command line. If these steps are not done, the command may fail.
export folder_path=<folder path> export private_registry=<local private registry> export component=<component name listed below> export digest=<component digest listed below> skopeo copy --all --authfile "${folder_path}/auth.json" \ --dest-tls-verify=false --src-tls-verify=false \ docker://cp.icr.io/cp/watsonx-data/${component}@${digest} \ ${private_registry}/cp/watsonx-data/${component}@${digest}
Component list and Digest:component: ibm-lh-cpg digest: sha256:0a4eebecebdb9a3bdb95cbe548059013babd2424477c302690b2724e10ad91ff component: lhconsole-ui digest: sha256:81757a0a64f809d2ede251155a2ddfef3cfe33783033d4e8ff3f85863cd31e4d component: lhconsole-api digest: sha256:4a1bb294f5c8aa421cadc63ef747aef46402737835ccb185c6b99952734bfbb7 component: ibm-lh-presto digest: sha256:e56e39027a1fde79fe1a0c2a72bbe78f2c8036ca3b312edec41b405ead0854b2 component: ibm-lh-mds-rest digest: sha256:66da29bc23f737b3a44bc5112064fad42587ed765a55628a697e95628b43f4ce component: ibm-lh-mds-thrift digest: sha256:4198dba6e4251d2d3b3c007774c5d487107f8d97e1723fa157c201f8d2129000 component: ibm-lh-milvus digest: sha256:9d010edd6f78db54b2e06fe142268cef4146e7473f40769a3c78110088d5dc72 component: lhplatform-ui digest: sha256:4c6f240bfa57ad377df2caa356b1c79476680930e2b36387865f4dc609dc764f component: lhplatform-api digest: sha256:1d1b9e8bd3c215eaa13372620737af48707225e62256e367c0f549666d9b034c component: cp.icr.io/cpopen/ibm-lakehouse-operator digest: sha256:8953b0657c3c262fcb7a2b10a16526d32ae302d5a2c419f5093a92544b6ad624
Online Environment:
To install the patch using the online IBM entitled registry, or to apply the hotfix using the images downloaded to the local private registry in the previous step, proceed with the following commands. Note that ${PROJECT_CPD_INSTANCE} refers to the project name where wxd is installed.
NOTE: When copy/paste each “oc patch” command below, ensure that it is contained on a single line without line breaks. Also, if any spaces are introduced by the copy/paste, they must be removed. If these steps are not done, the command may fail.
Apply the hotfix image (Use Private Registry Image Path in OPERATOR_IMG if airgapped):
export OPERATOR_IMG=cp.icr.io/cpopen/ibm-lakehouse-operator:2.2.0-207-20250701-003712-onprem-v2.2.0-hf2-amd64
export CPD_OPERATOR_NAMESPACE=<operator-namespace>
oc patch clusterserviceversion.operators.coreos.com/ibm-lakehouse-operator.v5.0.0 \
--type json \
-n $CPD_OPERATOR_NAMESPACE \
-p '[
{
"op": "replace",
"path": "/spec/install/spec/deployments/0/spec/template/spec/containers/0/image",
"value": "'${OPERATOR_IMG}'"
},
{
"op": "add",
"path": "/spec/install/spec/deployments/0/spec/template/spec/containers/0/imagePullPolicy",
"value": "Always"
}
]'
For the patch to register, delete the “ibm-lakehouse-controller-manager” pod in the Operator Namespace:
export CPD_OPERATOR_NAMESPACE=<operator-namespace>
export OPERATOR_POD=$(oc get po -o name -n $CPD_OPERATOR_NAMESPACE | grep "ibm-lakehouse-controller-manager-")
oc delete $OPERATOR_POD -n $CPD_OPERATOR_NAMESPACE
Wait 5-10 minutes for the new operator pod to reconcile and for wxdaddon, wxd, and wxdengine CRs to show Completed:
oc get wxdaddon,wxd,wxdengine
NAME VERSION SIZE RECONCILE AGE
wxdaddon.watsonxdata.ibm.com/wxdaddon 2.2.0 small Completed 2d1h
NAME VERSION SIZE RECONCILE AGE
wxd.watsonxdata.ibm.com/lakehouse 2.2.0 small Completed 2d1h
NAME VERSION TYPE DISPLAY NAME SIZE RECONCILE STATUS AGE
wxdengine.watsonxdata.ibm.com/lakehouse-presto-01 2.2.0 presto presto-01 small Completed RUNNING 2d1h
Was this topic helpful?
Document Information
Modified date:
17 July 2025
UID
ibm17239865