Oracle Cloud Infrastructure Documentation
Try Free Tier

Understanding Oracle Linux Package Management

OS Management Hub provides tools to manage packages and modules on Oracle Linux instances and groups, including scheduling updates, installing or removing packages, and editing modules.

For content based on vendor software sources, OS Management Hub provides package updates from the OCI regional yum server. For content from third-party and private software sources, package updates are provided from the repository URL you define for the source (see Repository URL and GPG Key).

Update Types Available for Oracle Linux

For Oracle Linux instances, OS Management Hub applies updates based on specific categories.

OS Management Hub Category Description
Security

An update that addresses security vulnerabilities found during development, testing, or reported by users. Security fixes usually have one or more associated CVE (Common Vulnerabilities and Exposure) names to identify the vulnerabilities.
Ksplice

An update used by Ksplice for installing zero-downtime security patches. The update job can include only Ksplice kernel updates, only Ksplice userspace updates, or both.

See Using Ksplice for Oracle Linux for how to configure an instance to receive Ksplice updates.
Bug Fix An update that fixes issues reported by users or discovered during development or testing.
Enhancement An update that introduces new features, improved functionality, or enhanced performance in the package's software.
Other An update that's not associated with any errata.

Package List Format

When providing a package list within the Console, you must use a valid package name format.

Valid formats are:

  • Package name (N)
  • Name, version, release, architecture (NVRA)
  • Name, epoch, version, release, architecture (NEVRA)
Format Type Format Examples
N (package name) name

git

python2
NVRA (name, version, release, architecture) name-version-release.arch

git-2.43.5-1.el8_10.x86_64

libselinux-2.8-6.el8.x86_64
NEVRA (name, epoch, version, release, architecture) name-epoch:version-release.arch

git-0:2.43.5-1.el8_10.x86_64

NetworkManager-adsl-1:1.30.0-13.0.1.el8_4.x86_64

The list can contain a combination of any of the formats. For example, a valid list would be:

python2
libselinux-2.8-6.el8.x86_64
NetworkManager-adsl-1:1.30.0-13.0.1.el8_4.x86_64

Generating a package list from an existing instance

You can run rpm -qa on a reference instance to collect a package list. For example, the format of the packages is:

pam-1.3.1-27.el8.x86_64
openssl-libs-1.1.1k-12.el8_9.x86_64
libreport-filesystem-2.9.5-15.0.4.el8.x86_64

Downloading a package list from an existing software source

You can download the package list from an existing software source and modify it as needed. See Downloading a Package List from a Software Source.

Using Ksplice for Oracle Linux

For OS Management Hub to apply Ksplice updates, Oracle Linux instances must have access to the Ksplice software sources and the Ksplice client installed.

For general information about Ksplice in Oracle Linux, see Oracle Linux Ksplice User's Guide.

Note

Ksplice doesn't apply to lifecycle environments. Instead, you manage content updates through versioned custom software sources and promotion. See Promoting a Versioned Custom Software Source to a Lifecycle Stage.

Adding the Ksplice software sources to the service

You must add the Ksplice software source to OS Management Hub. The availability of the software source can vary depending on instance type. For OCI instances, Ksplice is automatically available. For on-premises or third-party cloud instances, Ksplice requires an entitlement.

For on-premises or third-party cloud instances, ensure the management station's mirror storage has enough space for the Ksplice software source. Insufficient space can cause the mirror sync to fail and prevent the latest Ksplice updates from being applied. Ksplice software sources are large and can grow to several terabytes over the lifecycle of an Oracle Linux release. Allocate enough storage for each Oracle Linux version.

To check mirror volume capacity and sync status, see Viewing Management Station Details.

Attaching the Ksplice software sources to instances

After adding the software sources to the service, you must attach the software source to instances or groups. After attaching, verify that the individual instances have the appropriate Ksplice software sources. See Listing Software Sources Attached to an Instance.

Installing the Ksplice client on instances

Instances must have the Ksplice client installed to receive Ksplice updates from OS Management Hub. OCI instances use a different client than on-premises or third-party cloud instances.

OCI instances

OCI instances use the ksplice package for the Ksplice client.

For instances using a platform image, the ksplice package is installed by default. If using a custom image, you might need to install the ksplice package.

To verify the package is installed, see Listing Packages Installed on an Instance.

On-premises or supported third-party cloud instances

On-premises or third-party cloud instances use the ksplice-offline package for the Ksplice client.

  1. Check if the conflicting uptrack package is installed and remove it (uptrack-offline is ok).

    See the following (search for uptrack):

  2. Install the latest version of the ksplice-offline package.

    See the following (search for ksplice-offline):

Note

If the install job fails for the group, an individual instance in the group might have a conflicting Ksplice client installed. See Group manifest doesn't have uptrack, but ksplice-offline installation fails.

Verifying Ksplice Updates

Use the following methods to verify Ksplice updates are being applied.

Check the effective kernel

View the instance details and verify the effective kernel value has been updated. A blank value (-) indicates that no Ksplice kernel updates have been applied.

Check change history

View the change history report for the instance. Look for entries with a summary of "Update ksplice kernel" or "Update ksplice userspace". Select the entry's date to view job details.

Note

If you don't see Ksplice entries in the change history, the update job might have failed. See Listing Jobs Associated with an Instance and examine the error messages in any failed jobs.

Understanding Modules for Oracle Linux

Oracle Linux 8 releases provide modules, module streams, and profiles to enable the management of different versions of software within a single OS release.

Modules

Modules are a set of RPM packages that are grouped together and must be installed together. They can contain several streams that consist of multiple versions of applications that you can install. You enable a module stream to provide system access to the RPM packages that are contained in that module stream.

Module Streams
Module streams hold different versions of content contained within a module. Modules can have multiple streams, where each stream contains a different version of packages and their dependencies. Each stream receives updates independently.
Profiles
Profiles provide a list of certain packages that are installed at the same time for a particular use case. Profiles are also a recommendation by the application packagers and experts. Each module stream can have one or more profiles.

For more information about DNF modules, streams, and profiles, see Use DNF Modules and Application Streams in the Oracle Linux documentation.

For important guidelines, caveats, and warnings when performing package operations on modules and streams, see About Modular Dependencies and Stream Changes in the Oracle Linux documentation.

Module Status

The module stream can be in one of the following states:

  • Enabled: Stream can provide packages to the instance.
  • - (hyphen): Stream isn't enabled but can provide packages to the instance to satisfy package dependencies.
  • Disabled: Stream can't provide packages to the instance until enabled.

Package Management Tasks

Use the following tasks to manage packages for Oracle Linux instances and groups.

Instances

Package Management
Module Management
Software Source Management

Groups

Group Content Management

Was this article helpful?