Installation and upgrade issues
Use the troubleshooting tips and tricks in IBM Storage Fusion installation and upgrade.
Update operator OOMKilled error
To resolve the OOMKilled issue for the update operator, do the following resolution
steps:
Note: If the pod is in a CrashLoopBackOff state, delete the
isf-update-operator-*
pod. The pod comes back to running state for a couple of minutes. Do steps 1-4 in the
following resolution steps when the update operator pod is in Running state.- In the OpenShift® Container Platform console, go to .
- Search for UpdateManager in the Resources drop-down list.
- In the UpdateManagers, open the
versioninstance. - Go to the YAML tab.
- Increase the memory limit in
spec.resources.limits.memory. - After a couple of minutes, check whether the IBM Storage Fusion
clusterserviceversionobject ( tab) reflects the updated limit set for the update operator:- Search for the deployment name of the update operator
(
isf-update-operator-controller-manager) from the list of deployments underspec.install.spec.deployments. - In the specified deployment object, search for the container name
managerunder thespec.template.spec.containers. Also, check whether thelimits.memoryis equal to the one in theUpdateManagerCR. If not equal, change thememoryunderlimits.memeoryto the same limits value as mentioned in the UpdateManager CR in step 5. - Go to
tab and check whether the
limits.memoryis equal to the limit set in the previous step. If not equal, change thememoryunderlimits.memoryto the same limits value as mentioned in the previous steps.
- Search for the deployment name of the update operator
(
x509: certificate signed by an unknown authority
The x509: certificate signed by an unknown authority error can occur when you trigger a service
or firmware upgrade. A sample error is as follows:
Internal error occurred: failed calling webhook "mupdatemanager.kb.io": failed to call webhook: Post "https://isf-update-operator-controller-manager-service.ibm-spectrum-fusion-ns.svc:443/mutate-update-isf-ibm-com-v1-updatemanager?timeout=10s": x509: certificate signed by unknown authority
Do the following resolution steps:
- In the OpenShift Container Platform console, go to .
- From the
Resourcesdrop-down list, select MutatingWebhookConfiguration. - Select the
Labeldrop-down list and change it toName. - Search for
mupdatemanager. Check whether there are more than one instance ofmupdatemanager.*webhook. If so, take a backup of the older one and delete it. - Go back to page.
- From the Resources, select
ValidatingWebhookConfiguration. - Search for
vupdatemanager. Check whether there are more than one instance ofvupdatemanager.*webhook. If so, take the backup of the older one and delete it.