Oracle Cloud Infrastructure Documentation

ksplice-offline Package Fails to Install

Installing ksplice-offline might fail if there's an issue with the management station or if the system already has a Ksplice client installed. This applies to non-OCI instances only.

ksplice-offline not available from a management station

Error

The following errors indicate an issue with the management station:

Failed to download metadata for repo or Cannot download repodata/repomd.xml: All mirrors were tried

Resolution

See Download Errors in Job Error Log.

ksplice-offline conflicts with another Ksplice client

Error

The following errors indicate the conflicting uptrack package is installed:

exit status 1: Error: Transaction test error:
file /usr/lib/uptrack/regenerate-crontab from install of uptrack-offline-<version>.noarch conflicts with file from package uptrack-<version>.noarch
...

exit status 1: Error: Transaction test error:
file /usr/lib/uptrack/regenerate-crontab conflicts between attempted installs of uptrack-<version>.noarch and uptrack-offline-<version>.noarch
...

Resolution

Remove the conflicting uptrack package before installing ksplice-offline.

  1. Check if the conflicting uptrack package is installed and remove it (for non-OCI instances, uptrack-offline is ok).

    See the following (search for uptrack):

  2. Install the latest version of the Ksplice client package (ksplice for OCI and ksplice-offline for non-OCI).

    See the following (search for ksplice or ksplice-offline):

Note

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

Group manifest doesn't have uptrack, but ksplice-offline installation fails

If a one or more members of the group have uptrack installed, the installation job for the group fails. However, ksplice-offline successfully installs on all instances that don't have uptrack. You must remove the uptrack package from any outlier instances.

Workaround for the outlier instances:

For each outlier instance:

  1. Identify the problematic instance by viewing the job details for the ksplice-offline install job (see Listing Jobs Associated with a Group).
  2. Remove the uptrack package from the instance (see Removing Packages from an Instance).

  3. Install ksplice-offline package on the instance (see Installing Packages on an Instance).

For information on how group members might drift from what's on the group manifest, see Understanding Groups.