Related to:

OP5 Monitor 9.x.

OP5 Monitor migration.

Pre-migration process.

op5-extra-tools-check-migration

Problem

When following the official documentation for migration, there is a step to run the pre-migration compatibility. This allows the user to check for potential problems when migrating from OP5 Monitor version 8.4.x to 9.x. When following the steps, you may encounter this error:

No package op5-extra-tools-check-migration available. 
Error: Nothing to do

Possible Cause(s)

The op5-extra-tools-check-migration package is part of the "op5-monitor-updates" repository. If the .repo file for this repository is missing, or if the repository is disabled, the issue will be encountered.

Possible Solution(s)

Check if the .repo file exists

Run the command ls -l /etc/yum.repos.d/op5-release.repo

If the file does not exist, it can be created with the touchor nanocommand.

For reference, the file would look like this:

##### op5 Monitor
[op5-monitor-updates]
name=op5 Monitor Updates
baseurl=https://repos.op5.com/el$releasever/$basearch/monitor/8/updates
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-op5

##### op5 Epel
[op5-epel]
name=op5 EPEL
baseurl=https://repos.op5.com/epel/7/$basearch
enabled=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7

Check if the OP5 Monitor repository is enabled

Run the command grep "enabled" -B3 /etc/yum.repos.d/op5-release.repo

If you see enabled=0 for "op5-monitor-updates", edit the .repo file with a text editor and change it to enabled=1. See below for reference:

[root@op5-system ~]# grep "enabled" -B3 /etc/yum.repos.d/op5-release.repo
[op5-monitor-updates]
name=op5 Monitor Updates
baseurl=https://repos.op5.com/el$releasever/$basearch/monitor/8/updates
enabled=1

Related Articles

• Upgrade documentation
• Migration overview guide

If Issue Persists

• Please contact with our Client Services team via the chat service box available in any of our websites or via email to support@itrsgroup.com
  
  
  
• Make sure you provide to us:

- ANY LOG FILE OR DIAGNOSTIC

- ANY SCREENSHOT

- ANY VENDOR/VERSION OF WHAT THEY ARE TRYING TO CONNECT TO

-Any troubleshooting step already verified from the ones described in this article.