Known Issues

Learn about the issues you might encounter when using the OS Management service and how to work around them.

Note

For information about known issues related to other Oracle Cloud Infrastructure services, see Known Issues.
Internal error message displays on the Modules page in the Console

Details: OS Management support for module streams requires Oracle Cloud Agent 1.23.0 or later. If the minimum version of the Oracle Cloud Agent is not installed, clicking Modules (under Resources on the Managed Instance Details page) results in an internal error.

Workaround: If you encounter this internal error, update the oracle-cloud-agent package by following these steps.

  1. Log in to your instance. See Connecting to an Instance.
  2. Update the oracle-cloud-agent package.
    sudo dnf update oracle-cloud-agent

Direct link to this issue: Internal error message displays on the Modules page in the Console

Module streams from removed software sources are listed in the Console, CLI, and API
Details: If a software source with active module streams is removed (detached) from an instance, module streams from that software source still appear in the Console, CLI, and API. Attempting to install profiles from such module streams result in failed work requests for these profiles.
Important

We recommend that you do not remove software sources for active module streams and packages installed to the instance. Doing so removes access to important security patches and updates from the instance.

Direct link to this issue: Module streams from removed software sources are listed in the Console, CLI, and API

Manage instance groups are not supported with modules

Details: Managed instance groups are not currently supported with module features in OS Management.

Workaround: Currently, you can only manage modules, streams, and profiles on managed instances.

Direct link to this issue: Manage instance groups are not supported with modules

Changes made to module streams and profiles cannot be scheduled in the Console

Details: Enabling (or disabling) module streams and installing (or removing) profiles are performed immediately after saving changes in the Console. For more information, see Editing a Module on a Managed Instance.

Direct link to this issue: Changes made to module streams and profiles cannot be scheduled in the Console

Unable to manage CentOS instances

Details: OS Management cannot manage CentOS instances.

Workaround: No workaround is available currently.

Direct link to this issue: Unable to manage CentOS instances

Unable to patch DB systems

Details: The OS Management service is unable to apply patches to databases. The Database service provides its own solutions for applying patches to databases in bare metal and virtual machine DB systems.

Workaround: Follow the Database service procedures for applying patches to databases. For more information, see the Oracle Cloud Infrastructure Database Patch and Upgrade documentation.

Direct link to this issue: Unable to patch DB systems

Discrepancy in Windows updates displayed in Control Panel compared to the OS Management Console and API

Details: You might notice a discrepancy in the Windows updates shown in the Control Panel compared with the OS Management Console and API.

The OS Management service depends on the data it receives from the Windows Update Agent (WUA) API. When using the WUA API, the OS Management service does not have full access to all the APIs available as it does when using the Windows Server Update Service (WSUS) API. The policies controlling what you are allowed to do are different when you access the upstream Microsoft update service as opposed to when you create your own policies using WSUS.

Workaround: This behavior is expected at this point. We are aware of the issue and investigating improvements.

Direct link to this issue: Discrepancy in Windows updates displayed in Control Panel compared to the OS Management Console and API

Software sources can take several minutes to initially load in the Console

Details: When you display software sources in the Console, the software source can take several minutes to initially load, which can result in HTTP timeouts.

Workaround: If you encounter any HTTP timeout errors, refresh the browser.

Direct link to this issue: Software sources can take several minutes to initially load in the Console

Unable to use the OS Management service with instances found in ManagedCompartmentForPaaS compartments

Details: The OS Management service cannot be used with instances found 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 also cannot be used to manage updates for Database Cloud Service instances. For more information, see Unable to patch DB systems.

Direct link to this issue: Unable to use the OS Management service with instances found in ManagedCompartmentForPaaS compartments

OS Management Service Agent Plugin for Oracle Cloud Agent Fails When Installing Packages Using Third-Party Software Repositories

Details: Installing packages from third-party software repositories, such as Python Package Index (PyPI), can overwrite packages required by the underlying platform distribution, including the package dependency requirements for the OS Management Service Agent plugin.

Workaround: To prevent system dependencies from being overwritten, use virtual environments for Python development work. For more information about virtual environments, see the latest Python documentation.

Direct link to this issue: OS Management Service Agent Plugin for Oracle Cloud Agent Fails When Installing Packages Using Third-Party Software Repositories

Discrepancy in the status of the OS Management Service Agent plugin for disabled Oracle Linux 8 instances after update to Oracle Cloud Agent 1.16.0

Details: Beginning with Oracle Cloud Agent 1.16.0, the OS Management Service Agent plugin is enabled by default for Oracle Linux 8 instances. In Oracle Cloud Agent 1.15.0 and earlier, the OS Management Service Agent plugin was disabled by default for Oracle Linux 8 instances. Existing Oracle Linux 8 instances that were disabled before being updated to Oracle Cloud Agent 1.16.0 continue to be disabled after being updated to Oracle Cloud Agent 1.16.0. After upgrade, the Oracle Cloud Agent tab indicates that the plugin is enabled for these instances. However, the status for these instances indicates that the plugin is "Not Supported" with the message that "plugin is disabled in config."

Workaround: To manually resolve the discrepancy of the plugin status in the Oracle Cloud Agent tab:

  1. Open the navigation menu, click Compute, and then click Instances.
  2. Click the instance that you're interested in.
  3. Click the Oracle Cloud Agent tab.
  4. Toggle the Enable Plugin switch to Disabled.
  5. In the Disable Plugin confirmation dialog, click Disable to confirm the action.

If you want to enable the Oracle Cloud Agent Service Agent plugin on this instance, you must manually enable the plugin in the agent.yaml configuration file. After the plugin is enabled in the agent.yaml file, the plugin can be enabled or disabled by toggling the switch in the Oracle Cloud Agent tab.

To manually enable the plugin in the agent.yaml file:

  1. Log in to your instance. See Connecting to an Instance.
  2. Install the Oracle Cloud Agent software, if it is not already installed.
  3. Run the following sed utility script to enable the OS Management Service Agent plugin.
    sudo sed -i.saved -e '/^  osms:/,/^  [a-z]*:/{
    s/\(.*disabled:.*\)true/\1false/
    /^.*disableByOs:$/,/^  [a-z]*:/{
    /^.*-.*Oracle Linux Server.*:$/d
    /^.*-.*8.x/d}}' /etc/oracle-cloud-agent/agent.yml

    This script updates the osms configuration in the /etc/oracle-cloud-agent/agent.yml file as follows:

    • Changes the value for the disabled: parameter from true to false.
    • Removes the following lines from the disableByOS: section:
       - Oracle Linux Server:
            - 8.x
    Tip

    This script also backs up the configuration file to a file named agent.yml.saved. You can use the backup file to restore the agent.yml to the previous version of the file.

  4. Restart the Oracle Cloud Agent service.
    sudo systemctl restart oracle-cloud-agent.service

    It takes up to 10 minutes for the plugins to restart. After restart, the OS Management Service Agent plugin status changes to "Running" in the Oracle Cloud Agent Tab. The OS Management Service Agent plugin can then be managed using the Console or API.

  5. Proceed to Verifying the Status of the OS Management Service Agent Plugin.

Direct link to this issue: Discrepancy in the status of the OS Management Service Agent plugin for disabled Oracle Linux 8 instances after update to Oracle Cloud Agent 1.16.0

RESOLVED: Unable to manage AppStreams in Oracle Linux 8

Details: For Oracle Linux 8, the OS Management service does not currently support AppStreams, also known as modules or module streams.

Workaround: We are aware of the issue and working on a resolution. You can still update individual RPM packages but the versioning associated with modules is ignored using this method. For more information about AppStreams, see Oracle Linux 8: Managing Software on Oracle Linux.

Direct link to this issue: RESOLVED: Unable to manage AppStreams in Oracle Linux 8

RESOLVED: Oracle Autonomous Linux images cannot be managed by the OS Management service

Details: Instances that use the Oracle Autonomous Linux image cannot be managed by the OS Management service.

Workaround: This issue is resolved beginning with the August 2021 Oracle Autonomous Linux platform image.

Direct link to this issue: RESOLVED: Oracle Autonomous Linux images cannot be managed by the OS Management service

RESOLVED: Software source for UEK R6 not attached by default

Details: Beginning with the Oracle Linux 7 platform images launched in October 2020, Unbreakable Enterprise Kernel Release 6 (UEK R6) is the default kernel for Oracle Linux 7 instances. The OS Management service, however, attaches Unbreakable Enterprise Kernel Release 5 (UEK R5) as the software source for these images. As a result, you would not receive all available updates for your instance.

Workaround: This issue is resolved. For Oracle Linux 7 instances created beginning December 2021, the UEK R6 software source is attached by default. For Oracle Linux 7 instances created before December 2021, you must manually attach the UEK R6 software source to ensure that your instances are receiving all available updates.

Direct link to this issue: RESOLVED: Software source for UEK R6 not attached by default

RESOLVED: Unable to apply all Windows updates categorized as Other to a managed instance group

Details: OS Management does not currently provide an action for applying all Windows updates categorized as Other to a managed instance group.

Workaround: This issue is resolved. The Other category is now available for updates to managed instance groups. For more information, see Installing Updates on Windows Instances.

Direct link to this issue: RESOLVED: Unable to apply all Windows updates categorized as Other to a managed instance group