On April 23, 2025, OS Management reaches end of life (EOL). Effective now, the service is no longer available to you in regions where you are not already using OS Management, or to new users with new tenancies. Before the EOL date, we recommend that you migrate your managed instances to the OS Management Hub service. If you are an Oracle Autonomous Linux user, see Important Maintenance Event. For more information, see the Service Change Announcement.

Oracle Cloud Infrastructure Documentation

Resolving Incompatible Custom Software Sources

Some OS Management software sources might be incompatible with OS Management Hub. Use the migration assistant to identify incompatibilities and resolve any issues before migration.

Note

OS Management Hub has firmer rules for creating custom software sources. See Custom Software Sources for more information.

Software sources can be incompatible with OS Management Hub for the following reasons:

Software source contains packages from different OS versions or architectures

In OS Management Hub, custom software sources must be composed of packages from the same OS version and architecture.

If a mismatch is detected, the migration assistant reports the following issue and suggests the following action:

ISSUE: This software source has packages of multiple OS versions which are not supported in OSMH.
ACTION: Create separate OSMS custom software sources with packages from the same OS version and architecture.

To resolve this issue:

  1. Create separate custom software sources, one per architecture and OS version in OS Management. See Creating a Custom Software Source.
  2. After resolving the package incompatibility in OS Management, use the osms-to-osmh create custom-software-source command to create the custom software sources in OS Management Hub. 
    osms-to-osmh create custom-software-source

For example, suppose the osms-to-osmh discover custom-software-source command with the --verboseoption reports the following incompatibility:

ISSUE:  This software source has packages of multiple OS versions which is not supported in OSMH.

ACTION: Create separate OSMS custom software sources with packages from the same OS version and architecture.

DETAILS: 

The packages that are of OS version ORACLE_LINUX_8 are: 
 openssl-libs-1:1.1.1k-12.el8_9.x86_64
 oracle-epel-release-el8-1.0-5.el8.x86_64
 elfutils-default-yama-scope-0.189-3.el8.noarch
...
The packages that are of OS version ORACLE_LINUX_9 are: 
 langpacks-core-font-en-3.0-16.el9.noarch
 tracer-common-0.7.5-4.el9.noarch
 adobe-source-code-pro-fonts-2.030.1.050-12.el9.1.noarch
...

To resolve this issue:

  1. Create a custom software source for Oracle Linux 8 packages.
  2. Create a custom software source for Oracle Linux 9 packages.
  3. Use the osms-to-osmh create custom-software-source command to create the custom software sources in OS Management Hub.

Software source not added in OS Management Hub

Before a OS Management custom software source can be created in OS Management Hub, you must add all the vendor software sources that the custom software source is based on.

If missing vendor software sources are detected, the migration assistant reports the following issue and suggests the following action:

The Required VSS is not enabled in OSMH. Please Enable: <vendor-software-source-name>

To resolve this issue:

  1. Add the missing vendor software sources in OS Management Hub.
  2. After adding the vendor software sources, use the osms-to-osmh create custom-software-source command to create the custom software sources in OS Management Hub. 
    osms-to-osmh create custom-software-source

Software source has packages that don't support the specified OS version

In OS Management Hub, custom software sources must be composed of packages from the same OS version.

If a mismatch is detected, the migration assistant reports the following issue and suggests the following action:

ISSUE: This software source has packages which don't support the specified OS version.
ACTION: Add packages to separate OSMS custom software sources from the same OS version and architecture.

To resolve this issue:

  1. Create a separate custom software sources, one per architecture and OS version in OS Management. See Creating a Custom Software Source.
  2. After resolving the custom software issue in OS Management, use the osms-to-osmh create custom-software-source command to create the custom software sources in OS Management Hub. 
    osms-to-osmh create custom-software-source
  3. After successfully creating the custom software sources, revisit the software source assignments for your OS Management instances and adjust them as appropriate. See Managing Software Sources.