Upgrading IBM Cloud Pak for Watson AIOps
Upgrade an existing online or offline deployment of IBM Cloud Pak® for Watson AIOps 3.7.0 or later to 4.1.1.
You cannot use these instructions to upgrade deployments of IBM Cloud Pak for Watson AIOps 3.6.2 or earlier. For example, you cannot upgrade from IBM Cloud Pak for Watson AIOps 3.6.0 or 3.6.2 to IBM Cloud Pak for Watson AIOps 4.1.1.
Controlling upgrade
IBM Cloud Pak for Watson AIOps uses a versioning system of X.Y.Z, where X=version, Y=release, and Z=patch. For example, IBM Cloud Pak for Watson AIOps 3.7.2 is version 3, release 7, patch 2. IBM Cloud Pak for Watson AIOps upgrades can be release upgrades or patch upgrades.
Patch upgrades
Online deployments
Upgrades of online IBM Cloud Pak for Watson AIOps deployments to a higher patch, for example from IBM Cloud Pak for Watson AIOps 4.1.0 to 4.1.1, complete automatically if catalog polling is enabled. You elect to enable or disable catalog
polling when you install IBM Cloud Pak for Watson AIOps, and you can change this setting after installation if necessary. Automatic patch upgrade can also occur if you have not fixed the ibm-operator-catalog CatalogSource
to a specific image and the ibm-operator-catalog pods are restarted, even if catalog polling is disabled.
If you do not want your IBM Cloud Pak for Watson AIOps deployment to upgrade automatically when newer patches are available, then you must disable catalog polling and pin the image to a specific version. For more information, see Configuring automatic patch upgrades.
Offline deployments
Upgrades of offline IBM Cloud Pak for Watson AIOps deployments to a higher patch do not occur automatically, as the updated installation images must be manually mirrored to the offline repository first.
Release upgrades
Online deployments
Upgrades of online IBM Cloud Pak for Watson AIOps deployments to a higher release, for example from IBM Cloud Pak for Watson AIOps 3.6.2 to 3.7.0 or from 3.7.0 to 4.1.1 do not complete automatically, even if catalog polling is enabled. For a release upgrade, catalog polling must be enabled and the channel subscription must also be manually edited.
Offline deployments
Upgrades of offline deployments to a higher release version do not occur automatically, as the updated installation images must be manually mirrored to the offline repository first.
Upgrade procedure
Important: If you are planning to upgrade to Red Hat® OpenShift® Container Platform 4.12 as part of an upgrade to IBM Cloud Pak for Watson AIOps 4.1.1, you must complete the IBM Cloud Pak for Watson AIOps upgrade before you upgrade to Red Hat OpenShift 4.12.
The upgrade procedure depends on whether your deployment is an online or offline (air-gapped) deployment. For more information about online and offline deployments, see Installing IBM Cloud Pak for Watson AIOps.
Online deployments
You can upgrade an online deployment of IBM Cloud Pak for Watson AIOps with the Red Hat OpenShift console or command-line interface (CLI).