IKC 5.2.1 Semantic Automation Swap Model Issue Hotfix Installation Instructions

Step 1 and the substeps to download and copy the images to a local private registry for an air-gapped environment.  

Step 2 and the substeps to go through applying the patch using the online IBM entitled registry, or to apply the hotfix using the images downloaded to the local private registry from Step 1.  

Procedure 

1)   To apply, the patch in an air-gapped environment, proceed with the following steps.  

a)   Log in to the OpenShift console as the cluster admin. 

b)   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:  

${HOME}/.airgap/auth.json 

Or create an auth.json file that contains credentials to access icr.io and your local private registry. For example:

{ 

"auths": {  

"cp.icr.io":{"email":"unused","auth":"<base64 encoded id:apikey>"}, 

"<private registry hostname>":{"email":"unused","auth":"<base64 encoded id:password>"}  

} 

}

For more information about the auth.json file, see containers-auth.json - syntax for the registry authentication file.  

c)  Install skopeo by running:  

yum install skopeo 

d)  To confirm the path for the local private registry to copy the patch image, run the following command:  

oc describe pod <hotfix image pod> | grep -i "Image:" 

The <hotfix image pod> variable should be the pod name for your system.  

For example: 

oc describe pod semantic-automation-77859cd77-nhxx8 -n wkc | grep -i "Image:" 

Image:  

cp.icr.io/cp/cpd/semantic-automation-service:5.2.119@sha256:0a9bbcfe1f435810128bd1508c9ee08a1ae205a5fce36a2eeeee524ba27fe2f1 

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/cpd 

  source: cp.icr.io/cp/cpd 

For more information about mirroring of images, see Configuring your cluster to pull Cloud Pak for Data images. 

e)  Use the skopeo command with the appropriate auth.json file to copy the patch images from the IBM production registry (cp.icr.io/cp/cpd) 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 the“skopeo” command below, it is recommended to copy the command into a text editor to ensure there are no additional newline characters. Remove any additional newline characters. Then copy/paste the command from the text editor to the command line. If these steps are not done, the command may fail.  

skopeo copy --all --authfile "<folder path>/auth.json" \ 

--dest-tls-verify=false --src-tls-verify=false \ 

docker://cp.icr.io/cp/cpd/dc-main@sha256:e5f43d362d4a915eb5b051427d674aff46ee972e85ea6bce37c0d17e9e97c175 \ 

docker://<local private registry>/cp/cpd/dc-main@sha256:e5f43d362d4a915eb5b051427d674aff46ee972e85ea6bce37c0d17e9e97c175 

skopeo copy --all --authfile "<folder path>/auth.json" \ 

--dest-tls-verify=false --src-tls-verify=false \ 

docker://cp.icr.io/cp/cpd/semantic-automation-service@sha256:0a9bbcfe1f435810128bd1508c9ee08a1ae205a5fce36a2eeeee524ba27fe2f1 \ 

docker://<local private registry>/cp/cpd/semantic-automation-service@sha256:0a9bbcfe1f435810128bd1508c9ee08a1ae205a5fce36a2eeeee524ba27fe2f1