Upgrading Netcool Operations Insight on Red Hat OpenShift offline with a bastion host

Edit online

Use these instructions to upgrade an existing Netcool® Operations Insight® deployment from version 1.6.4 or 1.6.5 to 1.6.6, on an offline Red Hat® OpenShift® cluster, by using a bastion host.

Before you begin

  • Ensure that you complete all the steps in Preparing your cluster. Most of these steps were 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.
  • Configure persistent storage for your deployment. Only version 1.6.5 deployments with persistence enabled are supported for upgrade to version 1.6.6.
  • Before you upgrade to version 1.6.6, 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.6, if present, reverse any image overrides from the test 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.6 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.

About this task

You can upgrade your deployment on an offline Red Hat OpenShift cluster that has no internet connectivity by using an airgapped environment. This is done by creating an online bastion host that can download the Netcool Operations Insight CASE bundle from IBM CloudPaks, access the required images in the IBM Entitled Registry, and mirror them to a registry on the Red Hat OpenShift cluster. Then the Netcool Operations Insight operator and instance can be upgraded on the Red Hat OpenShift cluster.

Procedure

  1. Complete the steps in 1. Set up your mirroring environment.
  2. Complete the steps in 2. Set environment variables and download CASE files
  3. Complete the steps in 3. Mirror images

Upgrade the Netcool Operations Insight Catalog

  1. Complete the steps in 4.1. Create the catalog source

Upgrade the Netcool Operations Insight Operator

  1. Upgrade the Netcool Operations Insight Operator using CASE
    Run the following command on your bastion server:     
    oc ibm-pak launch \
$CASE_NAME \
--version $CASE_VERSION \
--namespace $NAMESPACE \
--inventory $CASE_INVENTORY_SETUP \
--args "--registry $TARGET_REGISTRY" \
--action install-operator
    Where namespace is the custom namespace to be used for your deployment.
  2. Verify the status of IBM Cloud Pak for Watson™ AIOps Event Manager.
    From the Red Hat OpenShift OLM UI, navigate to Operators > Installed Operators, and verify that the status of IBM Cloud Pak for Watson AIOps Event Manager is Succeeded.

Upgrade the NOI instance

  1. Note: If you already set up access to the target registry, skip this step.
    Create the target-registry-secret by running the following command: 
    oc create secret docker-registry target-registry-secret \
    --docker-server=$TARGET_REGISTRY \
    --docker-username=$TARGET_REGISTRY_USER \
    --docker-password=$TARGET_REGISTRY_PASSWORD \
    --namespace=$TARGET_NAMESPACE
  2. 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.
  3. Go to the All instances tab and select your instance. Edit the Netcool Operations Insight instance YAML.
    Update spec.version: 1.6.5 to spec.version: 1.6.6.
  4. Edit the Netcool Operations Insight properties to provide access to the target registry.
    1. Update spec.advanced.imagePullRepository so that it points to the target registry that you created.
    2. Set spec.entitlementSecret to the target registry secret.
  5. Select the Save button.
  6. Delete the CEM deployment by running the following command: 
    oc delete deployment <release-name>-ibm-cem-akora-app-cem
  7. If you cannot log in to the Netcool Operations Insight UI, for example Web GUI, after all pods are restarted, run the following command in the webgui pod: 
    oc exec -ti <release-name>-webgui-0 bash
/home/netcool/app/jazz/ui/bin/consolecli.sh RestoreConfigFromDb --username smadmin --password <smadmin password>
    Where <smadmin password> is the smadmin password.
    To obtain the smadmin password, run the following command:
    oc get secret <release_name>-was-secret -o json -n namespace | grep WAS_PASSWORD | cut -d : -f2 | cut -d '"' -f2 | base64 -d;echo
    Where:
    • <release_name> is the release name for the current cluster.
    • namespace is the namespace that Netcool Operations Insight is deployed into, which can be retrieved by using the oc project command.
    For more information, see Retrieving passwords from secrets.

What to do next

After upgrading, if the GitLab and SevOne observers are not listed in the YAML, run the oc edit noi command and add the following lines:
observers:
  gitlab: true
  sevone: true