Upgrading to IBM Concert Operate (OpenShift)
Upgrade an existing online or offline deployment of IBM Cloud Pak for AIOps 4.13.0 or later to IBM Concert Operate 5.1.5.
You cannot use these instructions to upgrade deployments of IBM Cloud Pak for AIOps 4.12.0 or earlier.
If IBM Netcool Operations Insight is deployed on the same cluster as IBM Cloud Pak for AIOps, ensure that Netcool Operations Insight is at version 1.6.13 or later before you upgrade IBM Cloud Pak for AIOps. Failure to do so may result in a broken Netcool Operations Insight deployment, as the upgrade process updates a shared component that is used by both applications.
Upgrade paths
The product uses a versioning system of X.Y.Z, where X=version, Y=release, and Z=patch. For example, IBM Cloud Pak for AIOps 4.13.1 is version 4, release 13, patch 1. Upgrades can be release upgrades, patch upgrades, or version upgrades (from the final release of one version to the first release of the next version).
You can upgrade by a maximum of one release at a time, and you can also upgrade directly from the final release of one version to the first release of the next version. If the release that you want to upgrade from is more than one release behind the release that you are upgrading to, then you must upgrade sequentially. For example, you cannot upgrade directly from IBM Cloud Pak for AIOps 4.9.0 to IBM Concert Operate 5.1.0, you must use the following sequence:
- Use the v4.10.1 documentation to upgrade from IBM Cloud Pak for AIOps 4.9.0 to v4.10.1.
- Use the v4.11.1 documentation to upgrade from IBM Cloud Pak for AIOps 4.10.1 to v4.11.1.
- Use the v4.12.0 documentation to upgrade from IBM Cloud Pak for AIOps 4.11.1 to v4.12.0.
- Use the v4.13.1 documentation to upgrade from IBM Cloud Pak for AIOps 4.12.0 to v4.13.1.
- Use this documentation to upgrade directly from IBM Cloud Pak for AIOps 4.13.1 (the final release of version 4) to IBM Concert Operate 5.1.0 (the first release of version 5).
Upgrade when a patch exists between the current and target release
When you upgrade IBM Cloud Pak for AIOps, some services and dependencies might upgrade to a patch in the current channel before they proceed to the target release in the target channel.
It is important to understand how the catalog works in IBM Cloud Pak for AIOps deployments. The catalog includes the channel for the current release and the channel for the previous release, and each release channel points to the latest patch that it has available. Both channels are needed so that upgrade paths can be resolved. For example, a catalog that uses the digest for v4.13.1 points to:
- The latest patch (v4.13.1) for the current release channel (v4.13)
- The latest patch (v4.12.0) for the previous release channel (v4.12)
After you deploy IBM Cloud Pak for AIOps, new patches might be added to your deployment's current channel. This means that when you update your catalog to a higher target channel as part of the upgrade procedure, the current channel might now point to a new latest patch (head). If a newer patch is available for the current channel, IBM Cloud Pak for AIOps upgrades to the latest patch in the current channel, even though you updated the catalog to use a channel for a higher release and did not change the subscription. This is because:
- Updating the catalog to use a higher channel makes the latest patch in the current channel available (which was not available at the time of your original deployment).
- IBM Cloud Pak for AIOps always updates to the newest patch that it has available for its current channel.
- Upgrade to a higher channel does not occur until the operator subscription is set to the new higher channel.
For example, consider upgrading from IBM Cloud Pak for AIOps v4.11.0 to v4.12.0:
- You have v4.11.0 installed. The catalog uses the v4.11.0 digest, and points to the v4.10.1 and v4.11.0 CSVs.
- You want to upgrade to 4.12.0. You update the catalog to the v4.12.0 digest, which points to the v4.11.1 and v4.12.0 CSVs.
- You are still subscribed to the v4.11 channel, so IBM Cloud Pak for AIOps upgrades from v4.11.0 to the latest patch in that channel, v4.11.1.
- Upgrade to v4.12.0 does not occur until you change your operator subscription channel from v4.11 to v4.12.
Guidance for upgrades that require an Red Hat OpenShift upgrade
Before you upgrade IBM Cloud Pak for AIOps, ensure that you are on a version of Red Hat OpenShift Container Platform that your current and target versions both support. This helps to ensure compatibility and avoid potential issues caused by platform API changes.
Example upgrade scenario
You have IBM Cloud Pak for AIOps 4.10.1 deployed on Red Hat OpenShift 4.15, and you want to upgrade to IBM Concert Operate 5.1.0 on Red Hat OpenShift 4.22.
The following table shows the supported Red Hat OpenShift versions for your current and target versions:
| Cloud Pak for AIOps/IBM Concert Operate version | Supported Red Hat OpenShift versions |
|---|---|
| 4.10.1 | 4.15, 4.16, 4.17, 4.18 |
| 4.11.1 | 4.16, 4.17, 4.18, 4.19 |
| 4.12.0 | 4.16, 4.17, 4.18, 4.19, 4.20 |
| 4.13.1 | 4.16, 4.17, 4.18, 4.19, 4.20, 4.21 |
| 5.1.0 | 4.16, 4.17.4.18, 4.19, 4.20, 4.21, 4.22 |
The upgrade steps for this example upgrade scenario are:
- Upgrade Red Hat OpenShift 4.15 to v4.18.
- Upgrade IBM Cloud Pak for AIOps 4.10.1 to v4.11.1.
- Upgrade IBM Cloud Pak for AIOps 4.11.1 to v4.12.0.
- Upgrade IBM Cloud Pak for AIOps 4.12.0 to v4.13.1.
- Upgrade IBM Cloud Pak for AIOps 4.13.1 to IBM Concert Operate 5.1.0.
- Upgrade Red Hat OpenShift to v4.22.
For advice on upgrading Red Hat OpenShift, see Upgrading a Red Hat OpenShift cluster.
Upgrade procedure
The following upgrade procedures are available for deployments on Red Hat OpenShift. Use the upgrade method that matches your deployment type from the following list:
For more information about online and offline deployments, see Installing .
The Online upgrade (CLI method) topic can be used to upgrade a starter or production deployment.