Online upgrade of Infrastructure Automation (console)

Before you begin

• Ensure that your cluster meets all of the prerequisites for deployment. For more information, see Planning.
• Red Hat OpenShift requires a user with cluster-admin privileges for the following operations:
  • Configure automatic catalog polling
  • Update the operator subscription

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 online Infrastructure Automation deployment.

1. Configure automatic catalog polling
2. Update the operator subscription
3. Verify the deployment
4. Post upgrade actions

1. Configure automatic catalog polling

Ensure that your catalog is set to automatically poll for updates.

Your ibm-operator-catalog CatalogSource object can be configured to automatically poll for a newer version, and to retrieve it if one is available. This triggers an automatic update of your deployment. Polling for updates is enabled by configuring the following polling attribute:

spec.updateStrategy.registryPoll

You might have already elected to automatically accept product updates by adding the polling attribute to your ibm-operator-catalog YAML when you installed Infrastructure Automation, installed an Infrastructure Automation hotfix from IBM Support, or when you installed another IBM Cloud Pak.

Use the following steps to check whether you already have a polling attribute set, and configure it if you do not.

Note: ibm-operator-catalog also contains the catalogs for other IBM Cloud Paks. If you have multiple IBM Cloud Paks installed on your cluster, and you enable the polling attribute, then automatic update is configured for all of them.

1. Log in to your OpenShift cluster console.

2. Go to Administration > Cluster Settings.

3. Click Configuration, and then scroll down and click OperatorHub.

4. Select Sources, scroll down, and click ibm-operator-catalog.

5. Click YAML to switch to the YAML view.

6. If there is not a spec.updateStrategy section, or spec.image is not set to icr.io/cpopen/ibm-operator-catalog:latest, then update the YAML to have the following in the spec block, and save it.

   spec:
     displayName: ibm-operator-catalog
     publisher: IBM Content
     sourceType: grpc
     image: icr.io/cpopen/ibm-operator-catalog:latest
     updateStrategy:
       registryPoll:
         interval: 45m
   

2. Update the operator subscription

Update the spec.channel value of the Infrastructure Automation operator's subscription to the release that you want to upgrade to, v4.9.

1. From OpenShift cluster console, select Home > Search.

2. From the Project list, select the project (namespace) that your IBM Infrastructure Automation subscription is deployed in. This is your IBM Infrastructure Automation project if your deployment is namespace scoped, or openshift-operators if your deployment has a cluster wide scope.

3. In the Resources list, select SUB Subscription. A list of subscriptions is displayed.

4. Click the subscription that has the name of ibm-infrastructure-automation-operator. A new window with the subscription details for ibm-infrastructure-automation-operator is displayed.

5. Click the value in the Update channel box. A new window called Change Subscription update channel is displayed.

6. Change the channel to v4.9 and click Save.

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).

3. Verify the deployment

Check the status of the Infrastructure Automation upgrade to make sure that it shows a status of Phase:Installing and eventually changes to Running.

1. Click Operators > Installed Operators.

2. From the Project list, select the project (namespace) that IBM Infrastructure Automation is deployed in if your deployment is namespace scoped, or openshift-operators if your deployment has a cluster-wide scope.

3. Locate IBM Infrastructure Automation in the list, and verify that the annotation underneath it shows 4.9.0 as version.

4. Select IBM Infrastructure Automation and then click IBM Infrastructure Automation under the Provided APIs column, and verify that it has a Status of Phase: Running, which means that your deployment is successful.

Note: Do not proceed until Infrastructure Automation has a status of Phase: Running.

4. Post upgrade actions

1. Clear your browser cache. Failure to do so will result in the error 502 Bad Gateway when viewing the Library, Instances, and Manage pages.

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