Oracle Cloud Infrastructure Documentation

Important Maintenance Event

Autonomous Linux service dependencies require updates to avoid a potential disruption with the service.

The Autonomous Linux service has different dependencies on other Oracle Cloud services for providing and managing autonomous updates. One of the services has modified policies and configurations which the Autonomous Linux service is unable to adjust without user intervention. Follow these steps to avoid a disruption in service.

Before You Begin

Autonomous Linux instances launched before April 24, 2024 have a service dependency on the OS Management service, which reaches end of life (EOL) on April 23, 2025. This change requires that you take the following steps.

If you only have a small number of Autonomous Linux instances to register with OS Management Hub, we recommend that you update your Autonomous Linux instances using the Console. If you have more than 10 Autonomous Linux instances to register with OS Management Hub, you can leverage the migration assistant.

Note

If you have questions or encounter any issues, contact Technical Support.

Before performing the service dependencies, you must do the following:

  • Set up the required IAM policy for OS Management Hub.

    This prerequisite is only required if you haven't enabled the OS Management Hub service for a compartment. You can use the policy advisor to quickly enable OS Management Hub for a compartment or you can manually create the policies.

    For more information, see OS Management Hub Policies.

  • If you are using the Notifications service with Autonomous Linux, amend your existing IAM policy to include the following:

    Allow any-user to use ons-topics in tenancy where request.principal.type='alx-notification'

  • If you plan to use the migration assistant to migrate Autonomous Linux instances, the migration assistant requires additional policies. Add the following required IAM policy to use the migration assistant. These policies can be added to a new group or to an existing group.

    allow group <user_group> to inspect compartments in tenancy
allow group <user_group> to use tag-namespaces in tenancy
allow group <user_group> to use instances in tenancy
allow group <user_group> to inspect work-requests in tenancy
  • The migration assistant CLI is used with Cloud Shell or the OCI SDK. If you plan to use Cloud Shell, you also need to add the following required IAM policy:

Using the Console

  1. Open the navigation menu, click Compute, and then click Instances.
  2. Click the instance that you're interested in.
  3. Under Resources, click OS Management and record the time that your Autonomous updates are applied.
  4. Click the Oracle Cloud Agent tab.
  5. Disable the following Oracle Cloud Agent service plugins by toggling the Enable Plugin switch to Disable:
    1. Disable the OS Management Service Agent plugin.
    2. Disable the Oracle Autonomous Linux plugin.

    This step disables the plugins on the instance. It takes up to 10 minutes for the change to take effect.

  6. Enable the OS Management Hub Agent plugin.
    1. For the OS Management Hub plugin, toggle the Enable Plugin switch to Enable.
    2. Select a service provided Autonomous Linux profile available in the root compartment. The default profiles are as follows:
      • Oracle Autonomous Linux 7: autonomous_linux_7_x86_64_profile
      • Oracle Autonomous Linux 8: autonomous_linux_8_x86_64_profile

      It takes up to 10 minutes for the change to take effect.

    Note

    For more information about how to enable and run plugins, see Managing Plugins with Oracle Cloud Agent.
  7. If required, modify the execution time for the daily autonomous update job:
    1. Under Resources, click OS Management.
    2. Next to Autonomous updates, click Edit.
    3. Enter the time you recorded previously.
  8. If you have additional software sources beyond the mandatory ones for Autonomous Linux, attach them to the instance.

    1. Confirm that you have added the software source to OS Management Hub. You must have permissions to the root compartment to add vendor software sources.

    2. Attach the software source to the instance.

Using the Migration Assistant

Before performing these steps using the migration assistant, you must do the following:

  1. The migration assistant is available in a specific directory on instances managed by OS Management Hub. You must have one instance registered with OS Management Hub to access the migration assistant. One option is using the Console procedure on an existing Autonomous Linux instance. If you have other instances using OS Management Hub, you can copy the utility from that instance.

  2. Install the migration assistant CLI using the Oracle Cloud Infrastructure (OCI) Cloud Shell or SDK.

To update your Autonomous Linux instances using the migration assistant, perform the following steps:

  1. If you are using additional software sources beyond the mandatory ones for Autonomous Linux:
    1. Add those software sources to OS Management Hub. You must have permissions to the root compartment to add vendor software sources.
    2. Create a registration profile for your Autonomous Linux instances with the additional software sources you added to OS Management Hub.
    Important

    Autonomous Linux instances have a minimum set of required software sources for each instance the service manages. For more information, see Mandatory Software Sources.

  2. View the registration profiles and record their OCIDs. You will need them in Step 5.
    1. Default profiles are available in the root compartment and are named:
      • Oracle Autonomous Linux 7: autonomous_linux_7_x86_64_profile
      • Oracle Autonomous Linux 8: autonomous_linux_8_x86_64_profile
    2. If you created registration profiles, view and record their OCIDs.
  3. Use the migration assistant to query for affected Autonomous Linux instances in the tenancy. 
    osms-to-osmh discover managed-instance --notmigrated

    In the command output, the ALX column indicates if an instance is an Autonomous Linux instance.

  4. From the command output in Step 3, copy the OCIDs and record the OS release (Oracle Autonomous Linux 7 or 8) for the instances. You will need them in Step 5.
    Note

    You can combine OS Management and Autonomous Linux instances together for the purpose of migration.

  5. Create a file in JSON input format for associating instances with profiles for batch migration.

    The JSON input format is as follows:

    {
    "managed-instance-ocid":"profile-ocid",
    "managed-instance-ocid":"profile-ocid",
    .....
}
  6. Use the migration assistant with the JSON file to migrate Autonomous Linux instances: 
    osms-to-osmh migrate managed-instance --mi-profile-map file://json-file -y

    Alternatively, you can also migrate an individual instance interactively using the following command:

    osms-to-osmh migrate managed-instance --managed-instance-id managed-instance-ocid

The migration assistant performs the follow actions:

  • Registers the instances with the Autonomous Linux service.
  • Ensures the software sources in your profile are attached to the instance.
  • Retains your scheduled job times for autonomous updates.

After migration, the job history for the Autonomous Linux instances will no longer be available in the OS Management service. Jobs performed after migration are viewable in the Autonomous Linux service.

Note

If you have questions or encounter any issues, contact Technical Support.