Objectives

In this Exercise you will learn how to upgrade MAS to the latest version.

It is not possible to use the MAS CLI docker to either update nor upgrade the MAS installation that is provided through TechZone. After a lot of tinkering I managed to find a more complex method that works - at least from MAS 9.0.0 to 9.0.2, as this exercise is build upon

Tip

You can see the release notes here: Maximo Application Suite Releases information


Before you begin:
This Exercise requires that you have:

  1. completed the pre-requisites required for all exercises
  2. completed the previous exercises

Login to MAS with the new MAS Admin account using the link to the MAS Home page:
MAS Login

Click on About in the upper right hand corner:
Select About

In this case it was a MAS 9.0.0:
About

Now we need to figure out what MAS 9.0 OpenShift catalog was used and if a newer one is available.
First open a terminal and run the MAS CLI docker container docker run -ti --rm --pull always quay.io/ibmmas/cli:
MAS CLI

Login to the OpenShift cluster using your kubeadmin account and click on Copy login command:
OCP Login Command

Click on Display Token and copy the oc login command in its entirety:
OCP Login Command

Run the command in the MAS CLI docker:
MAS CLI

Now the MAS CLI docker is authenticated against your OCP cluster. Execute mas update and enter yes in step 1.
Notice the Maximo Operator Catalog that has been used - in this case v9-240625-amd64 which is MAS 9.0.0.
Also notice that two newer versions are available (end of August), where 9.0.2 is the newest one:
MAS Update

Press Enter to select the default value, i.e. 1.
Step 5) Dependency Update Checks will be performed.

Tip

If the Dependency Update Check "hangs" then just rerun it in another window.

You will need the Installed Catalog and the Updated Catalog values later.
DO NOT PROCEED FROM HERE - enter n and Enter to escape from the mas update execution.
MAS Update

Go to your OCP and select Pipelines. If you are not seing the mas-masdevops-deploy pipeline, then select All Projects and search for it.
Open the mas-masdevops-deploy pipeline and click on the YAML tab:
OCP Pipelines

Scroll down until you find the Installed Catalog default value for the Maximo operator catalog version:
MAS DevOps Deploy YAML

Now replace the default value to the Updated Catalog value from the mas update command and click Save:
MAS DevOps Deploy YAML

Now the YAML is updated. Click on the pipelines in the bread crumps:
MAS DevOps Deploy YAML

Select the PipelieRunstab:
MAS DevOps PipelineRuns

You need to rerun the pipeline in order to upgrade to the version you selected:
MAS DevOps PipelineRuns

Now you see the original Succeeded pipeline and the rerun initiated one. Click on the Task status:
MAS DevOps PipelineRuns

You will see the execution of the pipeline has started. After a short while you get to the install-mas part.
Don't be scared when you notice FAILED - RETRYING .... messages, they will occure several times:
MAS DevOps PipelineRuns Logs

After quite a while all the steps in the pipeline will have rerunned. It will take almost as long as when you instatiated the
TechZone MAS 9.0 Certified Base image in the first place. In this case MAS 9.0 Core + Manage
MAS DevOps PipelineRuns Final

Login to MAS and check the About information. The MAS Core is upgraded to 9.0.2:
MAS About

And MAS Manage as well:
MAS About

Tip

You can now install the various Maximo Application Suite applications by following the MAS Devops Ansible Collection
and they will also be on the newest version.


Congratulations you have successfully instantiated and upgraded a MAS Techzone Certified Base Image and prepared it for use.