Offline upgrade of Infrastructure Automation
Use these instructions to upgrade Infrastructure Automation to 4.8.1.
This procedure can be used on an offline deployment of Infrastructure Automation, 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 Red Hat® OpenShift® Container Platform cluster with
oc login
for any steps that use the Red Hat® OpenShift® Container Platform command-line interface (CLI). - Red Hat OpenShift Container Platform requires a user with
cluster-admin
privileges for the following operations: - Ensure that your cluster meets all of the prerequisites for deployment. For more information, see Planning
Restrictions
- There are restrictions on which releases you can upgrade from. For more information, see Upgrade paths.
- The upgrade cannot be removed or rolled back.
Upgrade procedure
Follow these steps to upgrade your offline Infrastructure Automation 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:
-
Ensure that the IBM Catalog Management Plug-in for IBM Cloud Pak® (
ibm-pak-plugin
) is at the required level.Important:
ibm-pak-plugin
v1.9 and lower cannot process the Infrastructure Automation 4.8.1 catalog. You must ensure that you haveibm-pak-plugin
v1.10 or higher installed.-
Check which version of
ibm-pak-plugin
you have installed.Run the following command on your bastion host, portable compute device, or connected compute device if you are using a portable storage device.
oc ibm-pak --version
Example output:
oc ibm-pak --version v1.13.0
-
If the
ibm-pak-plugin
version is lower than v1.10.0, then you must download and install the most recent version.Follow the steps for your installation approach:
- Bastion host: Install the IBM Catalog Management Plug-in for IBM Cloud Pak®.
- Portable device: Install the IBM Catalog Management Plug-in for IBM Cloud Pak®.
-
-
Run the following command to set the environment variable that you need for upgrade.
export PROJECT_IA=<project>
Where
<project>
is the namespace (project) that Infrastructure Automation is deployed in.
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 device: 3 Mirror images
4. Update the catalog
Rerun step 5.1 or 5.2 of the air-gap installation procedure to update your catalog source.
Follow the steps for your installation approach:
- Bastion host: 5.2 Create the catalog source
- Portable device: 5.1 Create the catalog source
5. Update the operator subscription
Skip this section if you are upgrading from Infrastructure Automation v4.8.0 to v4.8.1, and proceed to section 6, Verify the deployment.
Update the spec.channel
value of the Infrastructure Automation operator to the release that you want to upgrade to, v4.8.
oc patch sub ibm-infrastructure-automation-operator -n ${PROJECT_IA} --type=json -p='[{'op': 'replace', 'path': '/spec/channel', 'value': 'v4.8'}]'
Important: You must only update the Infrastructure Automation subscription. You must not update the Infrastructure Management or Managed Services subscriptions (ibm-management-im-install
and ibm-management-cam-install
).
6. Verify the deployment
6.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.
oc get iaconfigs -n ${PROJECT_IA}
Example output:
NAME PHASE VERSION STORAGECLASS STORAGECLASSLARGEBLOCK AGE
ibm-ia-installer Running 4.8.1 rook-cephfs rook-ceph-block 8m44s
Important: Do not proceed until the message that Infrastructure Automation upgrade is Running is displayed.
6.2 Check the version
Run the following command and check that the VERSION that is returned is 4.8.1
.
oc get csv | grep -E "ibm-infrastructure-automation-operator|VERSION"
Example ouput:
NAME DISPLAY VERSION REPLACES PHASE
ibm-infrastructure-automation-operator.v4.8.1 IBM Infrastructure Automation 4.8.1 ibm-infrastructure-automation-operator.v4.8.0 Succeeded
6.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.8.1 rook-cephfs rook-ceph-block 8m44s
Important: Do not proceed until the message that Infrastructure Automation upgrade is Running is displayed.
7. Post upgrade actions
-
Clear your browser cache. Failure to do so will result in the error 502 Bad Gateway when viewing the
Library
,Instances
, andManage
pages. -
If you previously setup backup or restore on your deployment, then you must follow the instructions in Upgrading Infrastructure Automation backup and restore artifacts.