Upgrading a cloud deployment offline using the OLM UI and CASE (airgap)

Edit online

Use these instructions to upgrade an existing Netcool® Operations Insight® deployment from version 1.6.4 to 1.6.5, using the Red Hat® OpenShift® Operator Lifecycle Manager (OLM) user interface (UI) and Container Application Software for Enterprises (CASE).

Before you begin

Note: Upgrading cloud-based deployments from version 1.6.3.2 is not supported. You must first upgrade IBM® Netcool Operations Insight on Red Hat OpenShift to version 1.6.4 and then upgrade to version 1.6.5. For more information, see Upgrading and rolling back on Red Hat OpenShift in the version 1.6.4 documentation.

About this task

Ensure that you have completed all the steps in Preparing your cluster. Most of these steps should already have been completed as part of your previous Netcool Operations Insight deployment.
Ensure that you have an adequately sized cluster. For more information, see Sizing for a Netcool Operations Insight on Red Hat OpenShift deployment.
Your deployment must have persistent storage configured. Only version 1.6.4 deployments with persistence enabled are supported for upgrade to version 1.6.5.
Before you upgrade to version 1.6.5, if present, remove the noi-root-ca secret by running the following command:
```
oc delete secret noi-root-ca
```
Before you upgrade to version 1.6.5, if present, reverse any image overrides from the hot fix of the previous release.
1. Edit the custom resource (CR):
```
oc edit noi <release-name>
```
  Where <release-name> is the release name, for example, evtmanager.
2. Manually remove the tag, name, and digest entries of image overrides from the helmValuesNOI section of the YAML file.

All the required images for version 1.6.5 are either in the freely accessible operator repository (icr.io/cpopen), or in the IBM Entitled Registry (cp.icr.io) for which you will require an entitlement key.

Procedure

Download and install IBM® Cloud Pak CLI (cloudctl) version 3.17.0 from the cloud-pak-cli GitHub repository . Version 3.17.0 is the maximum supported version for installing Event Manager.
cloudctl verifies the integrity of the Netcool Operations Insight CASE's digital signature by default. If you want to verify the cloudctl binary, follow the instructions in https://github.com/IBM/cloud-pak-cli#check-certificatekey-validity. Extract the cloudctl binary, give it executable permissions, and ensure that it is in your PATH.
Download the IBM Netcool Operations Insight CASE bundle (ibm-netcool-prod) to your Red Hat OpenShift cluster by running the command:
```
cloudctl case save --case ibm-netcool-prod --outputdir destination_dir --repo https://raw.githubusercontent.com/IBM/cloud-pak/master/repo/case
```
Where destination_dir is a directory of your choosing, for example /tmp/cases

Run the following commands:

Upgrading to 1.6.5.1

export CASE_NAME=ibm-netcool-prod
export CASE_VERSION=1.5.1
export CASE_ARCHIVE=destination_dir/$CASE_NAME-$CASE_VERSION.tgz

Upgrading to 1.6.5

export CASE_NAME=ibm-netcool-prod
export CASE_VERSION=1.5.0
export CASE_ARCHIVE=destination_dir/$CASE_NAME-$CASE_VERSION.tgz

Where destination_dir is the directory that you downloaded the CASE bundle into in step 2.

Install the Catalog source by running the command:

cloudctl case launch \
  --case $CASE_ARCHIVE \
  --inventory noiOperatorSetup \
  --action install-catalog \
  --namespace openshift-marketplace

Where $CASE_ARCHIVE is specified in the previous step.

Upgrade the IBM Netcool Operations Insight Operator using CASE by running the command:
```
cloudctl case launch \
--case $CASE_ARCHIVE \
--namespace namespace \
--inventory noiOperatorSetup \
--action install-operator
```
Where namespace is the custom namespace to be used for your deployment.
From the Red Hat OpenShift OLM UI, upgrade the Netcool Operations Insight instance. Go to Operators > Installed Operators and select your Project. Then select IBM Cloud Pak for Watson™ AIOps Event Manager.
Go to the All instances tab and select your instance. Edit the Netcool Operations Insight instance YAML.
Upgrading to 1.6.5.1: Update spec.version: 1.6.5 to spec.version: 1.6.5.1.
Upgrading to 1.6.5: Update spec.version: 1.6.4 to spec.version: 1.6.5.
Select the Save button.
The logstash pod is replaced with the common-datarouting pod in version 1.6.5. Delete the logstash and spark deployments by running the following commands:
```
oc delete deployment <release-name>-logstash
oc delete deployment <release-name>-spark-master
oc delete deployment <release-name>-spark-slave
```
After you restart the noi-operator, confirm that the logstash and spark deployments are not recreated.

What to do next

If the

<release
name>-ibm-hdm-analytics-dev-dedup-aggregationservice

pod does not start up, restart the redis pods. For more information, see Service does not start up after upgrade.