Upgrading Infrastructure Automation
Upgrade an existing online or offline deployment of Infrastructure Automation to 4.9.0.
Upgrade paths
Infrastructure Automation uses a versioning system of X.Y.Z, where X=version, Y=release, and Z=patch. For example, Infrastructure Automation 4.8.1 is version 4, release 8, patch 1. Infrastructure Automation upgrades can be release upgrades or patch upgrades.
Stand-alone Infrastructure Automation
If you have a stand-alone deployment of Infrastructure Automation 4.4.x or later, then you can upgrade directly to the latest version of Infrastructure Automation.
Deployment of Infrastructure Automation with IBM Cloud Pak® for AIOps
You cannot use these instructions to upgrade deployments of Infrastructure Automation 4.7.1 or earlier.
You can upgrade by a maximum of one release at a time. If the release that you want to upgrade from is more than one release behind the release that you are upgrading to, then you must upgrade sequentially. For example, you cannot upgrade directly from Infrastructure Automation 4.5.0 to v4.9.0, you must use the following sequence:
- Use the v4.6.1 documentation to upgrade from Infrastructure Automation 4.5.0 to v4.6.1.
- Use the v4.7.1 documentation to upgrade from Infrastructure Automation 4.6.1 to v4.7.1.
- Use the v4.8.1 documentation to upgrade from Infrastructure Automation 4.7.1 to v4.8.1.
- Use this documentation, the v4.9.0 documentation to upgrade from Infrastructure Automation 4.8.1 to v4.9.0.
Controlling upgrade
Patch upgrades
Online deployments
Upgrades of online Infrastructure Automation deployments to a higher patch, for example from Infrastructure Automation 4.8.0 to 4.8.1, complete automatically if catalog polling is enabled. You elect to enable or disable catalog polling when
you install Infrastructure Automation, and you can change this setting after installation if necessary. Automatic patch upgrade can also occur if you have not fixed the ibm-operator-catalog CatalogSource to a specific image
and the ibm-operator-catalog pods are restarted, even if catalog polling is disabled.
If you do not want your Infrastructure Automation deployment to upgrade automatically when newer patches are available, then you must disable catalog polling and pin the image to a specific version. For more information, see Configuring automatic patch upgrades.
Offline deployments
Upgrades of offline Infrastructure Automation deployments to a higher patch do not occur automatically, as the updated installation images must be manually mirrored to the offline repository first.
Release upgrades
Online deployments
Upgrades of online Infrastructure Automation deployments to a higher release, for example from Infrastructure Automation 4.8.0 to 4.9.0 do not complete automatically, even if catalog polling is enabled. For a release upgrade, catalog polling must be enabled and the channel subscription must also be manually edited.
Offline deployments
Upgrades of offline deployments to a higher release version do not occur automatically, as the updated installation images must be manually mirrored to the offline repository first.
Upgrade procedure
Important: If you are planning to upgrade Red Hat OpenShift as part of an upgrade to Infrastructure Automation 4.9.0, then you must complete the Infrastructure Automation upgrade before you upgrade Red Hat OpenShift.
The upgrade procedure depends on whether your deployment is an online or offline (air-gapped) deployment:
Upgrading Infrastructure Management appliances
The following topics describe the process of upgrading Infrastructure Management appliances when a new release of Infrastructure Automation is available.
For more information about migrating from IBM Red Hat CloudForms or IBM Cloud Pak for Multicloud Management appliances to Infrastructure Automation, see these instructions to complete a full appliance replacement upgrade.
For more information about upgrading Infrastructure Management appliances, see:
For more information about migrating from an appliance installation to a Kubernetes (podified) installation of Infrastructure Management, see the following topic.