General Page
Steps to apply hotfix:
- Log in to the OpenShift Container Platform web console.
- Select the ibm-spectrum-fusion-ns (if IBM Fusion operator installed under this namespace) or <custom-ns> (if IBM Fusion operator installed into any other namespace) from the Projects drop-down.
- Go to Operators > Installed Operators.
- For isf-serviceability-operator-controller-manager and isf-application-operator-controller-manager, edit the IBM Fusion CSV in a YAML view.
Update the image for isf-serviceability-operator-controller-manager and isf-application-operator-controller-manager.
Note: For the offline customers, make sure to mirror the respective image. Refer to the mirroring instructions at the end for guidance.
For HCI:
Search for cp.icr.io/cp/fusion-hci/isf-serviceability-operator@sha256 and cp.icr.io/cp/fusion-hci/isf-application-operator@sha256 and replace all the images with the following image.
Version Image path Image version 2.10.0 cp.icr.io/cp/fusion-hci/isf-serviceability-operator@sha256
5bd3b53f8e662009b84af52b8261524462fef3996f6145b0d66619ef31d2bdab
2.10.0 cp.icr.io/cp/fusion-hci/isf-application-operator@sha256 3a387876d9a269121e38c185728ca2222a156037fcc5adf94b002635ca5050d1
For SDS:
Search for cp.icr.io/cp/fusion-sds/isf-serviceability-operator@sha256 and cp.icr.io/cp/fusion-sds/isf-application-operator@sha256 and replace all the images with the following image.
Version Image path Image version 2.10.1 cp.icr.io/cp/fusion-sds/isf-serviceability-operator@sha256
2a8206d5ec963cfced8e2e27980fd13ed211ac155540545b082a690c7c476ff1
2.10.1 cp.icr.io/cp/fusion-sds/isf-application-operator@sha256 782550ce3e5965cc1d5d152a2a1f015d2b8034f7699353c063557c9bee06effc - For callhomeclient_image_path and eventmanager_image_path, edit cr-version-cm configmap in a YAML view.
Update the callhomeclient_image_path, eventmanager_image_path, and logcollector_image_path fields of the Call Home, event manager, and log collector.
Note: For the offline customers, make sure to mirror the respective image. Refer to the mirroring instructions at the end for guidance.
For HCI:Version Image path Image version 2.10.0 cp.icr.io/cp/fusion-hci/callhomeclient@sha256 7f21cce18b21973fc70ded43eb48bb217d127e03656614baafc614c042be7c20 2.10.0 cp.icr.io/cp/fusion-hci/eventmanager@sha256 af3b60d5a4b35e7b34179d33b6afbe9addf9368d686819cd9d0a4e5a6e372d3a 2.10.0 cp.icr.io/cp/fusion-hci/logcollector@sha256 2898dc18e9ab2d1447478a326738099ba47c657987cc5c0a8925fff791d25176
For SDS:Version Image path Image version 2.10.1 cp.icr.io/cp/fusion-sds/callhomeclient@sha256 9597e4726e371da8996864fc6b2792906ee1cfff79710099b612bc0b7e556101 2.10.1 cp.icr.io/cp/fusion-sds/eventmanager@sha256 62912eb63db9026d7b0d18df8842cddc832f644531a2403e3ef5a16d159760f1 - Click Save.
The IBM Fusion detect changes automatically in the image and replaces the existing pod with the new one.
Note: The changes might take some time to reflect due to reconciliation delays.
Set TARGET_PATH variable as follows:
Note: Make sure you log into the local registry and IBM registry from the mirror host where you run the image copy skopeo command.export LOCAL_ISF_REGISTRY="<Your container registry host>:<port>"
export LOCAL_ISF_REPOSITORY="<Your image path>"
export TARGET_PATH="$LOCAL_ISF_REGISTRY/$LOCAL_ISF_REPOSITORY"
- Execute the skopeo command.
Example for HCI:skopeo copy --all --preserve-digests docker://cp.icr.io/cp/fusion-hci/isf-serviceability-operator@sha256:5bd3b53f8e662009b84af52b8261524462fef3996f6145b0d66619ef31d2bdab docker://$TARGET_PATH/isf-serviceability-operator@sha256:5bd3b53f8e662009b84af52b8261524462fef3996f6145b0d66619ef31d2bdabskopeo copy --all --preserve-digests docker://cp.icr.io/cp/fusion-hci/isf-application-operator@sha256:3a387876d9a269121e38c185728ca2222a156037fcc5adf94b002635ca5050d1 docker://$TARGET_PATH/isf-application-operator@sha256:3a387876d9a269121e38c185728ca2222a156037fcc5adf94b002635ca5050d1skopeo copy --all --preserve-digests docker://cp.icr.io/cp/fusion-hci/callhomeclient@sha256:7f21cce18b21973fc70ded43eb48bb217d127e03656614baafc614c042be7c20 docker://$TARGET_PATH/callhomeclient@sha256:7f21cce18b21973fc70ded43eb48bb217d127e03656614baafc614c042be7c20skopeo copy --all --preserve-digests docker://cp.icr.io/cp/fusion-hci/eventmanager@sha256:af3b60d5a4b35e7b34179d33b6afbe9addf9368d686819cd9d0a4e5a6e372d3a docker://$TARGET_PATH/eventmanager@sha256:af3b60d5a4b35e7b34179d33b6afbe9addf9368d686819cd9d0a4e5a6e372d3a
Example for SDS:skopeo copy --all --preserve-digests docker://cp.icr.io/cp/fusion-sds/isf-serviceability-operator@sha256:2a8206d5ec963cfced8e2e27980fd13ed211ac155540545b082a690c7c476ff1 docker://$TARGET_PATH/isf-serviceability-operator@sha256:2a8206d5ec963cfced8e2e27980fd13ed211ac155540545b082a690c7c476ff1skopeo copy --all --preserve-digests docker://cp.icr.io/cp/fusion-sds/isf-application-operator@sha256:782550ce3e5965cc1d5d152a2a1f015d2b8034f7699353c063557c9bee06effc docker://$TARGET_PATH/isf-application-operator@sha256:782550ce3e5965cc1d5d152a2a1f015d2b8034f7699353c063557c9bee06effcskopeo copy --all --preserve-digests docker://cp.icr.io/cp/fusion-sds/callhomeclient@sha256:9597e4726e371da8996864fc6b2792906ee1cfff79710099b612bc0b7e556101 docker://$TARGET_PATH/callhomeclient@sha256:9597e4726e371da8996864fc6b2792906ee1cfff79710099b612bc0b7e556101skopeo copy --all --preserve-digests docker://cp.icr.io/cp/fusion-sds/eventmanager@sha256:62912eb63db9026d7b0d18df8842cddc832f644531a2403e3ef5a16d159760f1 docker://$TARGET_PATH/eventmanager@sha256:62912eb63db9026d7b0d18df8842cddc832f644531a2403e3ef5a16d159760f1
Was this topic helpful?
Document Information
Modified date:
02 January 2026
UID
ibm17248261