Java not upgraded when upgrading Nolio Repo

book

Article ID: 210617

calendar_today

Updated On:

Products

CA Release Automation - Release Operations Center (Nolio)

Issue/Introduction

While trying to upgrade a Standalone 6.6 Nolio Repository to 6.7, we found it is not:

  • Upgrading the JRE used by the repo to 1.8.0_232; or
  • Updating the conf/version file to reflect 6.7.

 

Cause

This has been seen when there are two installations of the Nolio Repository and the upgrade is upgrading the other installation. 

The version of Java, version of Nolio (reflected in the conf/version file) and version of Nexus (seen via 'nexusVersion' in sonatype-work/nexus/conf/nexus.xml) were being properly updated in the other installation. 

Environment

Release : 6.6

Component : CA RELEASE AUTOMATION REPOSITORY

Resolution

Remove the other installation of the Nexus repository and then run the upgrade again. 

If you are not aware of where the other installation is located, run the upgrade with these two switches:

  • -Dinstall4j.alternativeLogfile=/tmp/repo_install.log
  • -Dinstall4j.keepLog=true

Example: ./nolio_repository_Linux_6_7_0_b81.sh -Dinstall4j.alternativeLogfile=/tmp/repo_install.log -Dinstall4j.keepLog=true

Once the upgrade is complete you can review the /tmp/repo_install.log and find the other location by searching for the string: used working dir

Once you have found the other location, make sure you have changed to that folder and stopped the service (in case it was running) using: ./nolio_repo.sh stop

Then either:

  • uninstall (using ./uninstall); 
  • or remove the folder

Finally, run the upgrade script again. When the upgrade prompts for where to upgrade/install, be sure to manually type the path of the existing installation that you need to upgrade.