Known Issues

Details

A You might have a policy issue 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

OS Management Hub supports fundamental operations for third-party and private sources, including attaching and detaching sources, applying updates, and installing packages. However, some operations for third-party or private sources aren't supported, such a viewing packages in these repositories or listing available packages for an instance. See Supported Actions with Third-Party and Private Sources.

Workaround

To install packages on an instance, you must provide the package name. Once installed, packages display on the installed packages list and any updates for the packages display on the available updates list.

We're working on a resolution.

Details

When creating an OCI instance within Compute using the Redwood preview of the Console, after enabling the OS Management Hub agent and selecting a profile, the instance might show 'Registration Failed' status in OS Management Hub.

Workaround

Option 1: After creating the instance, set the profile within OS Management Hub service.

1. Open the navigation menu and select Observability & Management. Under OS Management Hub, select Instances.
2. Under List scope, select the compartment that contains the instance.
3. Select the name of the instance.
4. Select Set profile.
5. Select the compartment and correct profile to use for registration.

6. Select Set.

   It can take several minutes for the status of the instance to update.

Option 2: Turn off the Redwood preview in the Console before creating the instance.

We're working on a resolution.

Details

The availability for some software sources might display incorrectly. If OS Management Hub released a software source (such as Oracle Linux 7 Extended Lifecycle Support) after you added your entitlement, the service might not automatically grant access to those software sources.

Workaround

Re-enter your Customer Support Identifier (CSI) to correct the availability of the software sources.

We're working on a resolution.

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

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

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 was 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 that specify versions or use filters that specify 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

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.

• Can't use private or third-party repositories
• Can't register OCI instances upgraded using Leapp
• 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