Known Issues

Details

When using shared storage in a high availability configuration, the software source mirror sync status on a management station might incorrectly show as 'Unsynced'. The sync status is with respect to the individual station's last sync job, not an immediate reflection of the actual content on the shared mirror storage. Therefore, the status might incorrectly show as 'Unsynced' if another station previously synced sources to the shared storage. In this case, even though a source shows as 'Unsynced' the content is actually synced and available to all instances using the station.

Workaround

To update the sync status, you can manually trigger a sync, or wait until the next sync job completes.

We're working on a resolution.

Details

A policy error was detected warning displays on the Overview page of OS Management Hub when the policy advisor can't find a specific set of policies and groups. If you've already set up policies, you might have named your groups and defined your policy statements differently than what the advisor expects (see What does the policy advisor create?). This causes the advisor to detect an error even when the policies are correctly configured.

See Using the Policy Advisor for more information.

Workaround

If OS Management Hub is functioning as expected, you can ignore the policy error notice.

Details

After deleting a management station, the station resource continues to remain in the list of stations with a mirror status of 'Unavailable'. If you attempt to delete the station again, you get the following error: Management station is already deleted.

Workaround

We're working on a resolution. Although in the station lists, the deleted stations can't be associated with registration profiles or used by instances. After 90 days, deleted stations are reclaimed and removed from the list.

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.

Details

A versioned custom software source might fail to promote if it was created with a series of packages filters that don't specify a version and the latest-only option enabled. The service creates the source without issue and displays it as Active. However, when you promote the source to a lifecycle stage, the promotion fails.

See also Troubleshooting: Lifecycle Promotion Fails.

Workaround

Create the versioned custom software source with a package list or use filters that specify package versions.

We're working on a resolution.

Details

When creating a custom software source, if you enable the latest-only option and specify filters to include multiple versions of a package, the older version might not be included in the custom software source. For example, if you specify an older version of openscap and specify the security-tools group (which includes openscap), only the latest version of openscap is included in the custom software source.

Workaround

Create the custom software source with a package list, disable latest-only, or use filters that specify only a single version of a package.

We're working on a resolution.

Details

When creating a custom software source with the auto-resolve option enabled, some exclude filters might be overridden. If you exclude a package that's a dependency of an included package, the exclude filter is sometimes ignored. For example, when including zsh and it's dependencies, but excluding acl (which is a dependency of zsh), the software source ignores the exclude filter and includes acl.

Workaround

Create the custom software source with a package list, disable auto-resolve, or use filters that specify only a single version of a package.

We're working on a resolution.

Details

A custom software source might display as Active, but show 'Packages available: -'. This occurs when a custom software source is created with a filter or a package list that specifies packages not contained within the included vendor software sources.

Workaround

Verify you've included the required vendor software sources. If using the auto-resolve option, you must also include the vendor software source of the dependent package.

If you're unsure which vendor software source a package requires, you can search for the package and identify the software source.

We're working on a resolution.

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.

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.

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. Select 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.

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.

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.

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'.

Details

Some Windows updates require manual installation. Often these updates require confirmation from the user before they can be installed, therefore OS Management Hub is unable to automatically install theses updates. For more information, see OS Management Hub can't install some updates.

Workaround

Sign in to the instance and install the update directly from the OS.

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.

These known issues have been resolved in OS Management Hub.

• Custom software source with large number of packages fails to create
• Instance name shows as UNKNOWN
• Custom software source might contain duplicate packages
• Versioned custom software source creation requires a package list
• OCI Events are not emitted
• Some resources aren't manageable with Terraform
• Oracle Cloud Agent 1.40 not yet available for Windows
• Instance reports aren't sorted by instance name
• Only vendor software sources displayed on Package Details page
• Advisory count not accurate in reports
• Unable to remove offline instances
• Unable to register compute instances in Oracle Cloud Infrastructure
• Package dependencies not resolved in filters for custom and versioned custom software sources
• Updates to the OS Management Hub plugin fail after updating JDK and JRE package
• Oracle Linux 8 oVirt vendor software sources aren't selectable