Upgrading Asset Repository to Automation assets

If you have your Automation assets instance in a different namespace from your Platform Navigator instance, you need to delete your Asset Repository instance and create a new operand in the same namespace as your Platform Navigator instance. To carry over your assets, you can perform a backup and restore as explained here.

Note: If you have multiple Asset Repository instances for a single Platform Navigator instance you will need to choose just one to upgrade and remove the others.

The Operator Lifecycle Manager (OLM) attempts to upgrade an operator when a new version is available to the cluster. If the operator subscription is set to Automatic approval, no action is required. Otherwise, approve the InstallPlan created by OLM to upgrade the operator.

To approve the InstallPlan click the Upgrade available link alongside the Asset Repository operator. You will then be prompted to Preview Install Plan and then Approve.

To upgrade the operator channel, go to the OpenShift console, select the Channel field from Subscription Details section for the Asset Repository operator, and change to the new channel. This manual step is required, even when automatic upgrades are configured.

Update the Asset Repository custom resource (installed instance). When Asset Repository was installed, the update function may have been configured to either happen automatically, or be done manually. In a situation where an upgraded Automation assets operator might support new versions:

• If your CR spec.version is set to use a channel, and the operator supports a newer version in that channel, your Asset Repository deployment is automatically upgraded.

• If your CR spec.version is set to use a specific version, upgrade your instance by updating the spec.version in the AssetRepository CR.

Updating the operand in Platform Navigator

Go to the Integration capabilities section of the Platform Navigator, which includes your instance. If your instance can be upgraded, you see a blue information icon that indicates there are new versions available.

Note: When upgrading you will need an updated license for the 2021.1.1 version.

To update the version and license of your operand, click the three-dot icon to see available options for editing the CR.

Updating the operand in the OpenShift Console

Navigate to Installed Operators > IBM Automation foundation assets operator > Asset Repository tab in the OpenShift console. You should see your operand. Click your instance and navigate to the YAML tab, where you can edit the CR spec and update the license and version.

Roll back to a previous version of the operand with one of these methods (similar to upgrade):

• Update spec.version in the AssetRepository CR.

• Use the Platform Navigator.

Before upgrading, you can choose to migrate information assets to your new installation.

1. Back up your data. Choose which information assets you want to migrate:

   • Remote assets - Navigate to the Remotes screen and note down all remote configurations (git urls, asset types, and so on).

   • Local assets - Delete all remotes so that only local assets remain, then navigate to the Asset Repository Browse Assets screen and download each asset in the list.

2. Install the 2021.1.1 Automation assets.

   To install the 2021.1.1 Automation assets deployment, follow the Installation instructions.

3. Restore your data.

   • Remote assets - Navigate to the Remotes screen and recreate all the remotes using the configuration noted down in the backup stage. See Remotes for more details.

   • Local assets - Navigate to your Asset Repository instance Browse Assets screen and use Add assets to upload all the assets downloaded in the backup stage.