New Nexus Repo: Action package is missing from the repository
search cancel

New Nexus Repo: Action package is missing from the repository

book

Article ID: 205510

calendar_today

Updated On:

Products

CA Release Automation - Release Operations Center (Nolio) CA Release Automation - DataManagement Server (Nolio)

Issue/Introduction

After creating a new Nexus repository we're seeing the following errors in our management server's nolio_dm_all.log file:

2020-12-21 18:20:03,114 [ActionsSyncTimer] ERROR (ActionPackConsole:418) - Action package {name='commons-net', fileName='commons-net-1.3.0.jar', packVersion='1.3.0'} is missing from the repository.

This is seen many times for various jar files. 

Environment

Release : 6.6

Component : CA RELEASE AUTOMATION RELEASE OPERATIONS CENTER

Cause

After creating a new Nexus repository that you configure the Management Server to use (via its conf/nolio-repo.properties file) you need to prepare it with the files expected to be available on the repository.

Resolution

There are two ways that you can prepare the new Nexus repository. Choose one of the following:

  • Backup/Restore the files from your old/original nexus repository server. This process is a sonatype nexus task. It is not supported by Nolio. However, this article may help: https://support.sonatype.com/hc/en-us/articles/213465118-How-to-Back-up-Nexus-for-Active-Standby-Failover; or
  • Copy over the action pack jar files that Nolio Release Automation expects to be available on the new repository server. This can be done following these steps:
    1. Open the management server's JMX MBean noliocenter:type=info.
    2. Then find the method syncWithRepository
    3. Select the "true" radio button and click Invoke.
      • This will transfer all of the jar files in the NACs actionslib folder to the nolio-actions nexus repository.
      • This WILL NOT copy over any files/artifacts that may have been copied to the nexus repository via the "Store artifact in local repository" artifact version option. If you need these files then you'll need to migrate the data from the old nexus repo to the new nexus repo (see above).