Offline upgrade of Infrastructure Automation

Use these instructions to upgrade Infrastructure Automation 3.7.0 or later to 4.1.0.

This procedure can be used on an offline deployment of Infrastructure Automation 3.7.0 or later, and can still be used if the deployment has had hotfixes applied. If you have an online deployment, follow the instructions in Online upgrade of Infrastructure Automation (CLI method).

Before you begin

Ensure that you are logged in to your OpenShift cluster with oc login for any steps that use the Red Hat® OpenShift® Container Platform command-line interface (CLI).

Restrictions

The patch cannot be removed or rolled back.

Installation procedure

Follow these steps to upgrade your offline Infrastructure Automation deployment.

Verify prerequisites
Download CASE files
Mirror images
Create the catalog
Modify resources to use the new channel
Update the operator subscription
Verify the deployment

1. Verify prerequisites

Ensure that your cluster still meets all the prerequisites for an air-gapped deployment.

Review the steps for your installation approach:

2. Download CASE files

On your OpenShift cluster, rerun step 2 of the air-gap installation procedure Set environment variables and download CASE files to download the latest CASE files.

Follow the steps for your installation approach:

Note: If you have an offline cache from a previous installation, you have two options to ensure that the latest CASEs are saved when you are using a case save command. You must:

Delete the existing CASE .tgz files from your offline cache.
Run a case save by using a different offline cache directory, and then copy the contents of that new directory into your existing offline cache.

Once you have the latest files in your offline cache, you can continue the airgap process using the offline cache directory.

3. Mirror images

Rerun step 3 of the air-gap installation procedure to mirror the updated images to the offline registry. Follow the steps for your installation approach:

Bastion host: 3 Mirror images to your final location
Portable compute device: 3 Mirror images to portable registry
Portable storage device: 3 Mirror images to portable registry

4. Create the catalog

Rerun step 5.2 of the air-gap installation procedure to update your catalog source.

Follow the steps for your installation approach:

5. Modify resources to use the new channel

You can modify the resources to use the new channel with the following commands.

oc -n <namespace> patch operandregistry infrastructure-automation --type=json -p='[
   {'op': 'replace', 'path': '/spec/operators/0/channel', 'value': 'v4.1'},
   {'op': 'replace', 'path': '/spec/operators/1/channel', 'value': 'v4.1'}]'

Note: Replace <namespace> with the actual namespace in which you deployed the Infrastructure Automation.

6. Update the operator subscription

Update the spec.channel value of the IBM Cloud Pak® foundational services operator subscription to v3.23.

oc patch subscription ibm-common-service-operator -n ibm-common-services --type=json -p='[{'op': 'replace', 'path': '/spec/channel', 'value': 'v3.23'}]'

Update the spec.channel value of the Infrastructure Automation operators subscription to the release that you want to upgrade to, such as v4.1.

oc patch subscription ibm-infrastructure-automation-operator -n <namespace> --type=json -p='[{'op': 'replace', 'path': '/spec/channel', 'value': 'v4.1'}]'

oc patch subscription ibm-management-cam-install -n <namespace> --type=json -p='[{'op': 'replace', 'path': '/spec/channel', 'value': 'v4.1'}]'

oc patch subscription ibm-management-im-install -n <namespace> --type=json -p='[{'op': 'replace', 'path': '/spec/channel', 'value': 'v4.1'}]'

Note: Replace <namespace> with the actual namespace in which you deployed the Infrastructure Automation.

7. Verify the deployment

7.1 Check Infrastructure Automation upgrade status

Check the status of the Infrastructure Automation upgrade to make sure the PHASE is Installing and eventually it changes to Running.

NAMESPACE=cp4waiops

oc get iaconfigs -n $NAMESPACE

Example output:

NAME               PHASE        VERSION   STORAGECLASS   STORAGECLASSLARGEBLOCK   AGE
ibm-ia-installer   Running      4.1.0     rook-cephfs    rook-ceph-block          8m44s

Important: Do not proceed until the message that Infrastructure Automation upgrade is Running is displayed.

7.2 Check the version

Verify that the patch has been successfully installed.

Log in to your OpenShift cluster's console.
Click Operators > Installed Operators.
From the project drop-down list, select the project (namespace) that Infrastructure Automation is deployed in.
Locate IBM Infrastructure Automation in the list and verify that the annotation underneath it shows 4.1.0.

7.3 Check the deployment

After a few minutes, run the following command from the CLI to verify that your Infrastructure Automation deployment is running again.

oc get iaconfigs.aiops.ibm.com -A

Example output:

NAME               PHASE        VERSION   STORAGECLASS   STORAGECLASSLARGEBLOCK   AGE
ibm-ia-installer   Running      4.1.0     rook-cephfs    rook-ceph-block          8m44s

Important: Do not proceed until the message that Infrastructure Automation upgrade is Running is displayed.

What to do next

If you previously setup backup or restore on your deployment, then you must follow the instructions in Upgrading Infrastructure Automation backup and restore artifacts.