Upgrade from 4.2.0.2 to 4.2.1.4

This section describes how customers can upgrade from version 4.2.0.2 to 4.2.1.4 in Docker environment.

Before starting an upgrade, make sure your current build is 4.2.1.2. To that, got to Administration -> About OpenIAM and verify the build configuration.

Verify cuttent build

To check from git status

  1. cd /usr/local/openiam/openiam-docker-compose
  2. Check from git status

Git status

  1. Check OpenIAM version in env.sh

Git status

To upgrade OpenIAM to version 4.2.1.4, perform the following steps:

  1. Run
sudo git checkout -b RELEASE-4.2.1.2-changes
sudo git add .
  1. Commit the changes to new branch with customizations.
sudo git commit -a -m "4.2.1.2-changes"

Changes

Note: If you encounter 'please tell me who you are' issue use the highlighted commands to setup your email and username.

  1. Do a merge in a new branch so you could keep original customized branch safe.
sudo git checkout -b update_to_RELEASE-4.2.1.4
sudo git pull origin RELEASE-4.2.1.4

Pulling into new branch

sudo git merge origin/RELEASE-4.2.1.4

Merging into new branch

Note: Please verify that OpenIAM version in env.sh is changed to 4.2.1.4. And if there are any merge conflicts follow the link to resolve those and merge afterwards.

  1. Restart Server Run
sudo ./shutdown.sh

and kindly wait for the containers to stop.

Then, run

sudo ./setup.sh
sudo ./startup.sh

After upgrading, to check the status of all the containers, execute

watch -n 5 ‘docker ps’

If some of the services are getting killed, follow the steps highlighted below:

  • The flyway container should fail:
docker ps -a

grep flyway with a non-zero exit.

  • Modify utilities/flyway/docker-compose.yaml, and uncomment FLYWAY_COMMAND: "repair" line

  • Deploy using./setup.sh && ./startup.sh

  • Modify utilities/flyway/docker-compose.yaml, and comment out FLYWAY_COMMAND: "repair" line.

  • Deploy using./setup.sh && ./startup.sh

  1. Check OpenIAM version in webconsole. Go to Administration -> About OpenIAM.

Upgraded build

NOTE: If rproxy container keeps restarting and shows logs similar to mentioned below.

rProxy log

The issue has to do with Ubuntu 20.04 syscalls not compatible with Docker version 19. Hence, the solution is to upgrade Docker version using below mentioned commands.

sudo apt update
sudo apt install apt-transport-https ca-certificates curl software-properties-common
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu focal stable"
apt-cache policy docker-ce
sudo apt install docker-ce

Note: .NET/PS connector versions to be used with OpenIAM version 4.2.1.4. should be at least 5.13.0.0 or higher. Please note that you must update connector if you use newer versions of the product. It is recommended to use the latest connector version. All .NET/PS connectors versions as at 5.24.0.0 version are backward compatible, hence updating it will not disrupt operation of OpenIAM versions 4.2.0 and higher.