Updating WebSphere Automation to version 1.6.4

You can update WebSphere Automation to version 1.6.4. Instructions are provided for both network-connected installations and installations in air gap environments.

Before you begin

If you are updating to WebSphere Automation 1.6.4 or 1.6.3 from 1.6.2, there is a known issue that can cause the upgrade to fail. For more information and instructions on how to work around the problem, see Update to WebSphere Automation 1.6.4 or 1.6.3 fails due to undefined storage classes.

If you are updating to WebSphere Automation 1.6 from 1.5:

  • Update to WebSphere Automation 1.6.0 from WebSphere Automation 1.5.3. If your WebSphere Automation installation is not version 1.5.3, update it to version 1.5.3 before you update it to version 1.6.0.
  • Before you update WebSphere Automation 1.5.3 to WebSphere Automation 1.6.0, you must first remove IBM Automation foundation.

Updating a network-connected installation

To update a network-connected installation,
  1. Update the update channel for the WebSphere Automation operator to v1.6. For more information, see Changing the update channel for an operator External link icon in the Red Hat® OpenShift® documentation.

    For patch updates, if the operator was configured with the Automatic update approval strategy, no action is needed. The WebSphere Automation operator automatically upgrades your installation.

    If the operator was configured with the Manual update strategy, follow the instructions for Manually approving a pending operator upgrade External link icon.

  2. If you are updating to WebSphere Automation 1.4 and plan to use the fix installation feature, restart each registered server. This action needs to be done only one time per server.

Updating an installation in an air gap environment

To update an installation of WebSphere Automation in an air gap environment, follow these instructions.
Note: Many of these steps link to steps in the airgap installation instructions. When you complete such a step in the airgap installation instructions, return to this page to find the next step in the updating process. Do not continue to the subsequent steps in the airgap installation instructions.
  1. Ensure that your cluster still meets all of the prerequisites for an air-gapped deployment.
  2. On your Red Hat OpenShift cluster, set the environment variables and download CASE files.
  3. Mirror the updated images to the offline registry. As you follow these instructions, use 1.6.4 as the value for $CASE_VERSION. The version of IBM Cloud Pak foundational services (ibm-cp-common-services) appears as 3.23.x.
  4. Configure ImageContentSourcePolicy and create a global pull secret.
  5. Update the catalog source.
  6. Update the update channel for WebSphere Automation to v1.6.

    For more information, see Changing the update channel for an operator External link icon in the Red Hat OpenShift documentation. For patch updates, if the operator was configured with the Automatic update approval strategy, no action is needed. The WebSphere Automation operator automatically upgrades your installation.

    If the operator was configured with the Manual update strategy, follow the instructions for Manually approving a pending operator upgrade External link icon.

  7. Validate the installation.

Updating custom roles

If you created custom roles with the can_view_websphere_inventory permission in a previous version, you must change them to use a different permission. Using the UI with such a custom role in a later version results in an error when the UI displays some of the pages.

For instructions on updating the custom roles, see The MyCustomRole role includes an invalid permission: can_view_websphere_inventory.

What to do next

Validate the installation and access the WebSphere Automation UI.

If your installation stalls during an update, you might need to update the WebSphereSecure custom resource (CR) to use a storage class that supports ReadWriteMany (RWX) access mode. For more information, see Installation stalls during an update.