Known Issues

Versioned custom software source creation requires a package list

Details

A problem has been identified with creating a versioned custom software sources using filters. The resulting versioned custom software source can't be promoted through a lifecycle. The filtering options for versioned custom software sources are temporarily unavailable.

Workaround

Create the versioned custom software source using a package list. See Creating a Custom Software Source. We're working on a resolution to re-enable filtering for versioned custom software sources.

Older platform images or Bring Your Own Images will not register

Details

OS Management Hub requires Oracle Cloud Agent (OCA) version 1.40 or later. This version of the OCA agent is included with the April 2024 Oracle Linux and Microsoft Windows platform images. Instances created with older platform images or with Bring Your Own Images that don't have the required OCA version will not have the OS Management Hub agent plugin and can't register with the service.

Workaround

After instance creation, allow the Oracle Cloud Agent updater to install the latest OCA that includes OS Management Hub support. Then register the instance using the Oracle Cloud Agent tab in the Console. The automatic update process can take up to an hour.

Custom software source might contain duplicate packages

Details
Custom software sources that use the oci_included vendor software source might contain duplicate packages.
Workaround

The duplicate packages have no negative effects on the instances that use the custom software source. We're working on a resolution.

Custom software source with large number of packages fails to create

Details

Custom software sources that contain too many packages remain in the 'Creating' state for a long period and then fail.

Workaround

Limit packages to 90,000 or less. To reduce the number of packages, use filters, a package list, or reduce the number of vendor software sources included in the source. If you need more packages than the limit, create multiple custom software sources each with a smaller number of packages.

We're working on a resolution.

Installed Windows update displays as an 'Available update'

Details
Some Windows updates that require a reboot will continue to display as an 'Available update' even after they've been installed.
Workaround
Restart the instance to fully apply the update. After the instance restarts, the update will display as an 'Installed update'.

No option to edit a module for a group

Details
OS Management Hub doesn't provide an option to edit a module for a group using the Console at this time.
Workaround
We're working on a resolution. As a workaround, you can use the API or CLI to edit the module. Or, in the Console you can first remove the module and then add the module with the updated module stream configuration.

Instance name shows as UNKNOWN

Details
OS Management Hub displays UNKNOWN for the instance name when the hostname of the instance starts with a number.
Workaround

We're working on a resolution. As a workaround, change the hostname to start with a letter. See the following support articles for how to change the hostname:

Can't use private or third-party repositories

Details
You can't use your own private or third-party yum repositories or mirrors with OS Management Hub. The service, however, doesn't interact with nor interfere with content from these repositories.
Workaround

We're working on a resolution to manage content from private and third-party repositories using OS Management Hub.

As a workaround, you can manually add custom repository files to /etc/yum.repos.d on an instance registered with OS Management Hub and then manage those repositories outside of the service. OS Management Hub won't disable these repositories. However, scheduled update jobs won't update content from private or third-party repositories.

Can't patch Oracle Databases

Details

OS Management Hub doesn't apply patches to databases. If you're using the OCI Database service, it provides its own solutions for applying patches to databases in bare metal and virtual machine database systems.

Workaround

Follow the Database service procedures for applying patches to databases. See the Database Update documentation.

If you're not using the OCI Database service, follow the Oracle Database documentation.

Can't manage PaaS instances

OS Management Hub can't manage instances in ManagedCompartmentForPaaS compartments. This compartment is created on behalf of the user for use with Oracle Platform Services on Oracle Cloud Infrastructure. For more information about this compartment, see Information About Supported Platform Services.

OS Management Hub can't manage updates for Database service instances. For more information, see Can't patch Oracle Databases.

Can't register OCI instances upgraded using Leapp

Details

An OCI instance that was upgraded using Leapp can fail to register with OS Management Hub when using the Console. When you enable the OS Management Hub agent plugin, the Console presents registration profiles matching the OS version from when the instance was created, not the upgraded OS version.

Important

You can't use Leapp to upgrade instances managed by OS Management Hub. Upgrading managed instances isn't supported.
Workaround

Use the following workaround to register an instance that was previously upgraded with Leapp:

  1. Open the navigation menu, click Compute, and then click Instances.
  2. Click the instance that you want to register.
  3. Click the Oracle Cloud Agent tab.
  4. Enable the OS Management Hub Agent.
  5. Select a profile to use to register the instance.

    The available profiles match the OS version originally used to create the instance, not the upgraded OS version. Choose any available profile or create a profile for the older OS version.

  6. Open the navigation menu and click Observability & Management. Under OS Management Hub, click Instances.

    After a few minutes, the instance appears in a ‘Registration failed’ state because the registration profile doesn't match the instance's OS version.

  7. Click the name of the instance.
  8. Click Set profile, and then select the compartment and profile to use for registration.

    The available profiles match the upgraded OS version running on the instance.

  9. Click Set.

    Note

    It can take up to 10 minutes for an instance to register with the service.

Resolved Issues

Some resources aren't manageable with Terraform

Details

OS Management Hub isn't fully compatible with Terraform. Some operations including attaching registration profiles to OCI instances and managing scheduled jobs aren't yet supported in Terraform.

Resolved

2024-05-16

The Terraform provider for OS Management Hub has been updated.

Oracle Cloud Agent 1.40 not yet available for Windows

Details

OS Management Hub requires a minimum of Oracle Cloud Agent version 1.40. This release isn't yet available for Microsoft Windows. You can't register Windows instances with the service until it's available.

Resolved

2024-05-01

As of May 1, 2024, the Microsoft Windows version of the Oracle Cloud Agent is available.

To check the Oracle Cloud Agent version on an instance and to upgrade, see Updating the Oracle Cloud Agent.

Instance reports aren't sorted by instance name

Details
The security updates, bug updates, and instance activity reports aren't sorted by instance name.
Resolved
2024-04-23

Only vendor software sources displayed on Package Details page

Details

The package details page shows the software sources associated with a package. Currently, the page only shows vendor software sources. If the package is part of a custom or versioned custom software source, the page doesn't reflect that.

Resolved
2024-04-23

Advisory count not accurate in reports

Details

The advisory count is incorrect for the security updates report and bug updates report. The advisory count lists the number of packages with security updates available for the instance, not the count of advisories against the instance.

Resolved
2024-04-23

Unable to remove offline instances

Details
OS Management Hub is unable to remove offline instances.

Offline instances include:

  • Instances that are no longer in communication with the service.
  • Unregistered instances that couldn't communicate with the service at the time that they were unregistered.
Resolved
2024-04-23

Unable to register compute instances in Oracle Cloud Infrastructure

Details
OS Management Hub is unable to register compute instances in Oracle Cloud Infrastructure.
Resolved
2024-04-23

Package dependencies not resolved in filters for custom and versioned custom software sources

Details
OS Management Hub doesn't automatically resolve package and module dependencies. You're responsible for determining which packages or modules are required.
Workaround
This issue was resolved.
Resolved
2024-04-23

Updates to the OS Management Hub plugin fail after updating JDK and JRE package

Details

If the JRE or JDK packages are updated and the mgmt_agent systemd service hasn't been restarted, the OS Management Hub plugin update will fail and the instance will lose communication with the service. Additionally, the instance might show as inactive or offline. The instance will not check in with the service or run update jobs until the mgmt_agent service restarts.

Workaround

This issue is resolved.

Resolved
2023-08-30

Oracle Linux 8 oVirt vendor software sources aren't selectable

Details

The Oracle Linux 8 oVirt 4.4 and Oracle Linux 8 oVirt 4.4 Extras software sources aren't available when adding vendor software sources to OS Management Hub.

Workaround

This issue is resolved.

Resolved
2023-10-17