Known Issues for OS Management

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

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.

Workaround

We are aware of this issue. There is no workaround but to ensure that you do not remove software sources for active module streams and packages installed to the instance.

Details

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

Workaround

We're working on a resolution. Currently, you can only manage modules, streams, and profiles on managed instances.

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.

Workaround

We're working on a resolution.

Details

OS Management cannot manage instances that use CentOS streams.

Workaround

There is no workaround. OS Management does not support instances using CentOS streams.

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 Update documentation.

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 in time. We are aware of the issue and investigating improvements.

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.

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.

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.

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.yml configuration file. After the plugin is enabled in the agent.yml 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.yml 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.

Details

The Oracle Instant Client 18.3 basic package can't be updated to 19.5 on instances that were created before March 18, 2020 because of changes to packaging.

sudo yum remove oracle-instantclient18.3-basic
sudo yum install oracle-instantclient19.5-basic

Workaround

To update Oracle Instant Client, manually remove Oracle Instant Client 18.3, and then install 19.5. Use the following commands:

sudo yum remove oracle-instantclient18.3-basic
sudo yum install oracle-instantclient19.5-basic

Details

On Oracle Autonomous Linux instances that were created after March 18, 2020, Oracle Instant Client is not installed by default.

Workaround

To install Oracle Instant Client 19.5, you must manually install the package. Use the following command:

sudo yum install oracle-instantclient19.5-basic

Details

On Oracle Autonomous Linux instances that were created after December 9, 2020, the Oracle Instant Client repository (ol7_oracleinstant client) is not available by default.

Workaround

To add the repository, you must first install the oracle-release-el7 release package and then enable the ol7_oracle_instantclient repository. You can then install the appropriate Oracle Instant Client version package. Use the following commands:

sudo yum install oracle-release-el7
sudo yum-config-manager --enable ol7_oracle_instantclient

These known issues have been resolved in OS Management.