Installation and upgrade issues

Use the troubleshooting tips and tricks in IBM Fusion installation and upgrade.

Update operator OOMKilled error

Problem statement
The pods go into crash loop state with the OOMKilled error after OpenShift® Container Platform upgrade.
Resolution
To resolve the OOMKilled issue for the update operator, do the following resolution steps:
  1. Go to IBM Fusion clusterserviceversion object (Operators > Installed Operators > IBM Fusion operator > YAML tab).
  2. Search for the deployment name of the isf-update-operator (isf-update-operator-controller-manager) from the list of deployments in the clusterserviceversion object under spec.install.spec.deployments.
  3. In the specified deployment object, search for the container name manager under the spec.template.spec.containers and increase the memory limit in the resources.limits.memory.
  4. After changing the limits in the IBM Fusion clusterserviceversion, the update operator pod restarts with the new limits.
  5. If the OOMKilled issue still persists, then follow the steps 1 - 4 again.

x509: certificate signed by an unknown authority

Problem statement
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
Resolution
Do the following resolution steps:
  1. In the OpenShift Container Platform console, go to Home > Search.
  2. From the Resources drop-down list, select MutatingWebhookConfiguration.
  3. Select the Label drop-down list and change it to Name.
  4. Search for mupdatemanager. Check whether there are more than one instance of mupdatemanager.* webhook. If so, take a backup of the older one and delete it.
  5. Go back to Home > Search page.
  6. From the Resources, select ValidatingWebhookConfiguration.
  7. Search for vupdatemanager. Check whether there are more than one instance of vupdatemanager.* webhook. If so, take the backup of the older one and delete it.

Known issues

If the IBM Fusion installation is stuck in the custom-ns namespace with the error deployment of isf-serviceability-operator not ready before timeout, ignore it and continue with the installation.